Is it possible to add user specified "paramters" to a manually triggered deploy step in pipelines?

[Steve Melrose]

I'm currently POC'ing out doing full CI + CD within Bitbucket Pipelines for part of our application. For the most part, I have this working. We have the following simple pipeline,

• "Build" - `npm install`, build the Docker image, etc.
• "Test" - Run tests within said Docker image
• "Deploy" - Deploy Docker image to ECS. This step has a manual trigger.

We have a monolithic repository that deploys to multiple services. The reason for this- rightly or wrongly -is there's a good amount of core code overlap between each service. This isn't something we can easily change any time soon.

A problem we have is that when we come to do a deploy, due to some long running processes within some of those services, we don't necessarily want to deploy to every service every time.

Ideally, when we click "Deploy" in the Bitbucket Pipeline and the dialogue comes up telling us what will be deployed, we'd love at this point to have the user provide parameters. For example, we could add a list of tick boxes so the user can specify which services to deploy to.

I'm 99% sure this isn't currently possible with Bitbucket Pipelines, but I'm curious if it's on the roadmap at all?

Failing that, does anyone have any ideas of how we could achieve what we want within the current functionality available? I considered having an individual deploy step for each service, but it looks like we wouldn't be able to just click the ones we wanted to deploy. You have to have a sequential dependency chain, and you can't do manually triggered deploy steps in parallel. It's a shame as CircleCI supports this kind of tree structure, but their manually trigger/deploy stuff just isn't as nice.