[LEAK BITBUCKET SECRET] masking secret dont affect when using printenv to artifacts

[Prima Adi Pradana]

Need this addressed.

this is really dangerous since every pipeline as long user have access the could executed a pipeline inside our own branch

https://cloud.google.com/blog/topics/threat-intelligence/bitbucket-pipeline-leaking-secrets

could we somehow disable artifacts if there is some command running or like blocked printenv completely

[Aloy Scanlan _Product Forge_]

Hey @Prima Adi Pradana - isn't this the case for all cloud CI/CD tools - not just Pipelines? It looks like the exact same thing happens with Github Actions: https://github.com/orgs/community/discussions/24928

If you're concerned about this happening, you could use something like a Dynamic Pipeline to look through any CI workflows before they run and not run any that look to be printing secrets to files.