Use enum for variable in custom pipeline

Question

I would like to deploy to different environments in our Bitbucket pipeline. Our environments are limited to three, and I'd like to limit the options available when starting the pipeline.

A pipeline right now looks like this:

custom: 
deploy-cosmos-to-env: 
     - variables: 
        - name: ENVIRONMENT 
     - step: *plan-cosmos 
     - step: *apply-cosmos

I would like to limit the possible variables:

variables:
  - name: ENVIRONMENT
    enum: [dev, staging, prod]

Is this possible?

PS. How do you copy paste into this editor? It decimates new lines, even in code blocks.

unknown · Answer

I had already voted for that issue :)  The monorepo approach has brought some headaches so far, but its also very convenient in some ways. I will sleep on it, thanks for your input.

Radek Antoniuk · Answer

Ah, got it, indeed this is somewhat an unusual setup I'd say, because from a single repo (that is usually a single service) you're controlling actually multiple service to multiple environments. See https://jira.atlassian.com/browse/BCLOUD-18771

I don't know what your repository looks like, but personally I would probably split those services into 3 separate repositories if they should be managed independently.

unknown · Answer

I have no need to control permissions, a user that has repo access has deploy access.

Unfortunately it is not the same, it doesn't work. Deployments are limited to be declared once per pipeline. This is my full pipeline, without the definitions:

Now all custom steps are able to be run individually and target all three different environments. This enables me to run one specific commit and one specific piece of infrastructure.

With deployments, this block would have to be repeated for each environment, and that is if deployments could be repeated.