Open
Description
Current Situation:
Every pipeline step that uses environments automatically creates a new deployment. This seems to be wanted behavior.
Problem
Access to an environment
might be also needed for other reasons than deployments. Like running integration tests (deployment already done; we want to assure correct behavior of latest deployment)
Possible Solution
Can we add an option to avoid an automatic deployment always when using environment
?
An idea might be to set an environment variable like AUTO_DEPLOYMENT=false
.
Additional information