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
Describe the solution you'd like
The current solution doesn't allow specifying Targets (or Target Tags) to deploy to.
Describe alternatives you've considered
The alternative option is to use a octopus release deploy CLI with a --deployment-target flag. However, it's not as convenient as existing GitHub Action.
Additional context
This feature can be useful if you have multiple environments (e.g., QA01, QA02, etc).
In this case, you may have a single deployment Step with either a tag that matches all Deployment Targets or tags of all Deployment Targets. Then, in the CD pipeline, you would specify a single/multiple environment to deploy the release to.
This should have the same logic as the Include specific deployment targets checkbox when deploying a release manually via UI.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
The current solution doesn't allow specifying Targets (or Target Tags) to deploy to.
Describe alternatives you've considered
The alternative option is to use a octopus release deploy CLI with a
--deployment-target
flag. However, it's not as convenient as existing GitHub Action.Additional context
This feature can be useful if you have multiple environments (e.g., QA01, QA02, etc).
In this case, you may have a single deployment Step with either a tag that matches all Deployment Targets or tags of all Deployment Targets. Then, in the CD pipeline, you would specify a single/multiple environment to deploy the release to.
This should have the same logic as the
Include specific deployment targets
checkbox when deploying a release manually via UI.The text was updated successfully, but these errors were encountered: