You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: