Skip to content
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

Config splits cannot be applied to Acquia Cloud environments #1298

Closed
arknoll opened this issue Apr 3, 2017 · 4 comments
Closed

Config splits cannot be applied to Acquia Cloud environments #1298

arknoll opened this issue Apr 3, 2017 · 4 comments
Labels
Bug Something isn't working

Comments

@arknoll
Copy link
Contributor

arknoll commented Apr 3, 2017

Issue on d.o.: https://www.drupal.org/node/2865912

We have to wait for this to be fixed before merging in the config-split default CM strategy.

@danepowell ^

@danepowell
Copy link
Contributor

danepowell commented Apr 3, 2017

tl;dr: because Acquia Cloud defines the /config/default directory to be the vcs config directory, whereas most modules (including config_filter/config_split) assume you are using the default sync directory, there's currently no way to define config splits for Acquia Cloud environments.

A quick workaround might be to redefine the sync directory to be /config/default and pass this as the deploy config directory key instead of vcs. Or try the custom Drush command bircher suggested. Not sure what the best long-term solution is yet.

@grasmash grasmash added the Bug Something isn't working label Apr 3, 2017
@grasmash
Copy link
Contributor

grasmash commented Apr 4, 2017

@arknoll @danepowell this is resolved by #1299, right?

@danepowell
Copy link
Contributor

It should be.

@arknoll
Copy link
Contributor Author

arknoll commented Apr 4, 2017

yes. this can be closed

@danepowell danepowell changed the title Cross-posting an issue with config-split/config-filter here Config splits cannot be applied to Acquia Cloud environments Apr 4, 2017
@grasmash grasmash closed this as completed Apr 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants