Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Support CDEs for config splits #1311

Closed
grasmash opened this issue Apr 4, 2017 · 4 comments
Closed

Support CDEs for config splits #1311

grasmash opened this issue Apr 4, 2017 · 4 comments
Labels
Enhancement A feature or feature request

Comments

@grasmash
Copy link
Contributor

grasmash commented Apr 4, 2017

When a new CDE is created on ACE, config.settings.php should activate a corresponding config split. All CDEs should probably use the same split. E.g., 'ci' or 'cde'.

@grasmash grasmash added the Enhancement A feature or feature request label Apr 4, 2017
@grasmash
Copy link
Contributor Author

grasmash commented Apr 4, 2017

@arknoll @geerlingguy Let me know if you think this makes sense.

@arknoll
Copy link
Contributor

arknoll commented Apr 4, 2017

Yeah, this is the same sort of problem I was mentioning with Acquia Search on CDEs. I think the most logical would be to force it into the dev split. If a team wants to override it they can just adjust their settings.php below blt's config include.

@geerlingguy
Copy link
Contributor

I would default to dev. Failing that, cde. It's definitely going to be different than the typical ci environment, if devs can log into sites running on them and use them like they would one of the normal cloud environments.

@grasmash
Copy link
Contributor Author

grasmash commented Apr 6, 2017

I've created an ah_other split to handle both RA envs and CDEs. #1331

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement A feature or feature request
Projects
None yet
Development

No branches or pull requests

3 participants