In working on #870 one improvement that reflects an isolated piece of work is updating our environment-based actions to use GitHub's environments functionality.
This means that instead of having distinct secrets for environments, and instead of having distinct workflows that are nearly identical except for the secrets used, we could DRY out our workflows and secrets.
This will involve:
- Setting up the environments in github UI.
- Creating new secret names (that have no env prefix).
- Refactoring our various build-{foo} workflows to ideally have just one workflow related to deployment.
Once this is done we should be able to also consolidate and streamline our workflows.
In working on #870 one improvement that reflects an isolated piece of work is updating our environment-based actions to use GitHub's environments functionality.
This means that instead of having distinct secrets for environments, and instead of having distinct workflows that are nearly identical except for the secrets used, we could DRY out our workflows and secrets.
This will involve:
Once this is done we should be able to also consolidate and streamline our workflows.