This is something that we need. When would we expect to get an update on this?

5 years since original request. hope to see this feature in Bitbucket before i retire 👴🏼

Hi Team Any Update on this..?

is there any news?

Long time no update 

We are looking forward as well to seeing this feature implemented. Also, it would be nice to be able to specify the default value for each variable,

This is an important feature especially from a security perspective. When will this be implemented ? It shouldn't be too hard, should it ?

Would like to ask where this feature is at? Is it still low on the priority list? It would really help with providing a gate check for deploying to certain environments if say a secure password was required to deploy to said environment everytime the pipeline is triggered.

I was surprised this is not a thing, given that repo-level secure variables exist. Since `bitbucket-pipelines.yml` does not provide a separate `secrets:` keyword in addition to `variables:`, I would expect all variables to be treated as secrets.

https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/ and https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/ should probably mention this problem and this Jira issue, so that people won't accidentally log secrets.

I think that's crucial to have secured pipeline variables. Sometimes, we have to use the custom pipelines.