staging/prod through workspace specific variables/resources

Original message was deleted

rubenf•5/27/23, 1:15 PM

Taking inspiration from the way vite shadows .env files, we are gonna make resources/variable to be made workspace specific overridable: https://vitejs.dev/guide/env-and-mode.html#env-files

The way it will work is that priority of resolution will be:

<path>.<workspace>.resource/variable.yaml
<path>.resource/variable.yaml

When values will be pulled, they will be under the form:

<path>.resource/variable.yaml

And so it will require manual intervention to make them workspace specific.

The exception will be for secrets, secrets will always be pulled as workspace specific (unless pulled with --plain-secrets) since because of their encryption they are workspace specific

rubenf•5/27/23, 1:17 PM

^ we will update the guidance on how to do staging/prod, there are 3 ways of achieving this:

separate them in folders staging/prod (this change would have no effect)
separate them in different workspaces (this change make it possible)
separate them in different instances (this change make it possible)

The 3 ways are equally valid and will mostly depend on your requirements