Allow usage of environment scoped variables outside of the start/stop actions
Problem to solve
Currently scoped environment variables can only be used when a given job has the environment:name set up (duh).
Problem: environment:action can only be start or stop
Problem: setting environment:name without setting environment:action implies environment:action: start
So let's say I want to make a manual job for dumping the database. Naturally, I would like to read database credentials from a scoped variable just like a deployment would do. If I set an environment:name so I can get scoped variables, I also screw up the deployment environment metadata, because this helper job will now be considered the latest deployment.
Intended users
Devon
Further details
Proposal
I can see two ways to fix this issue:
A: Allow arbitrary environment:action values. Values other than start/stop don't mess with the deployment environment metadata. Plus we can keep track of these tasks, have action buttons more accessible, etc.
B: don't assume environment:action: start when environment:name is not set. Keeps action-less tasks anonymous. Has potential to break stuff (I myself don't have the habit to set this).