On the new Access Controls page in Bitbucket Cloud - there is a reference that says "Access controls don't apply to add-ons."
The Learn More link goes to: https://confluence.atlassian.com/x/TY5qMw
But that documentation makes no reference to the meaning of how access controls apply (or don't apply) to add-ons.
Does anyone know more about this reference?
Thanks for your question.
When we say "Access controls don't apply to add-ons," we mean that any add-ons you've installed for your team will continue to work even if you've enforced an access control (such as IP whitelisting).
This is because if access controls did apply to add-ons and you enforced an IP whitelist, you'd have to whitelist the IP address of each add-on's server(s).
If there's demand for the ability to lock out add-ons we'll take a look at it, but for the initial rollout we went with the 80% use-case, which is that customers will want add-ons to keep working (or they can choose not to install any add-ons).
Hope that helps!
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot