-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment doesn't import configuration #1597
Comments
Running a config import with the verbose flag locally does include the expected output:
So this doesn't seem to be entirely a problem with the verbose flag being set. |
Actually, I'm finding that this isn't simply an issue with the logging missing. The configuration is not being imported as expected. If I try to import with drush, I see that my change is un-imported:
|
Some additional information here. If I ssh into the server and run the import command alone, this works as expected:
|
I've been able to trace this issue down to this line of the verbose output:
Is there some configuration I'm missing here? cm:
dirs:
sync:
path: ${cm.core.path}/default If I set this variable in my cm:
core:
dirs:
vcs:
path: ${cm.core.dirs.sync.path} But is it expected that I should need to set this value in this version of BLT ( |
build.yml in 8.8.3 contains the following:
This is indeed missing |
My system information:
8.8.3
When I deploy code on ACE with a change to a configuration file.
I get the following output:
And I expected that the update would be logged in the same manner as it is locally:
My untested assumption is that this has something to do with the verbose flag that is set as part of
ace_deploy
:blt deploy:update -Denvironment=$target_env -Dblt.verbose=true
The text was updated successfully, but these errors were encountered: