Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
3.1.0
-
None
Description
According to docu:
When executing commands from within the local configuration folders or subfolders, the local configuration is used.
...
The local configuration is created as a copy of the current configuration (used during execution of the customize-local-config command), which you can edit to define project specific prototypes or dependencies.
When running mgnl customize-local-config - this is not the case (anymore), instead, the globally installed configuration is used as a "template" to create the new local config.
Example:
The folder mgnl-bundles contains a local config
~/mgnl-bundles/
├── 6.2-CE-with-demo
├── cli-downloads
├── mgnl-cli-prototypes
└── mgnl-cli.json
now within ~/mgnl-bundles/6.2-CE-with-demo, run:
mgnl customize-local-config
The file
/mgnl-bundles/6.2-CE-with-demo/mgnl-cli.json
should be a copy of
/mgnl-bundles/mgnl-cli.json.
...
But that's not the case ... instead the new created files seems to be a copy of the globally installed config.
Additional note
I herby can confirm, that jumpstart does use the local config.
However, I have not checked all commands regarding which config - local or global - is used.
This should be checked, and I hope it can be easy checked with some hopefully existing tests.