Pipelines - Dynamic Deployment Name

[Chris Romp]

Now that we have multiple environments under each deployment type (Test, Staging, Production), is it possible to use variables for deployments in pipelines?  We're trying to dynamically assign feature branches to environments.

feature/*:
  - step:
      name: Deploy to Feature Environment
      deployment: $variable

Or even something like this:

pipelines:
  custom:
    feature-deployment
      - variables:
          - name: ENV_NAME
      - deployment: $ENV_NAME

I've tried calling a custom pipelines with variables from the rest API, but even when I do so the custom pipeline doesn't like the `$variable` for `deployment` at all.

[Chris Romp · Accepted solution]

Added as a feature suggestion here: https://jira.atlassian.com/browse/BCLOUD-19611

If you want to see this implemented, please go vote on the feature (click vote, not just watch).

[milos.jajac]

I am looking for this as well. It would be immensely useful to allow for dynamic deployment names (ex. use $BITBUCKET_BRANCH for the name, and create a deployment env for each important branch).

However, it is not yet supported. Here is a similar thread.

[Chris Romp]

https://jira.atlassian.com/browse/BCLOUD-19611

[Paul Selibas]

Removed