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

Is there a way to define a secret override for *any* multi-dev? #54

Open
jedihe opened this issue Mar 1, 2024 · 2 comments
Open

Is there a way to define a secret override for *any* multi-dev? #54

jedihe opened this issue Mar 1, 2024 · 2 comments

Comments

@jedihe
Copy link

jedihe commented Mar 1, 2024

The docs mention environment overrides, which can be set for dev, test, live.

For multi-devs, is there a way to define a single override that is used in any multi-dev? or is it required to set an override for each multi-dev? (e.g. pr-1234).

I think using the value-for-multi-devs when first setting a secret, then overriding for dev, test, live envs should work as well. I just want to know what's possible in order to choose what works best for us.

Thanks!

@jedihe
Copy link
Author

jedihe commented Mar 4, 2024

From Drupal Slack:

The design was that the default value should be set up to be meaningful in any context where there is no override, e.g. all the multidevs. It should be possible to make an env override for the dev environment, although I realize I am not 100% sure.

@stovak
Copy link
Member

stovak commented Mar 5, 2024

@jedihe thanks for the feature request. We're surfacing it internally and we'll hit this thread back if/when there's a decision to add the feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants