I just exceeded my Stash license and I was clueless why this happened. After some investigation I found out the following scenario:
This is a strange catch22 situation in my opinion. The reason I want to have the auto-add function is to automatically add the users logging in to Stash to the licensing scheme via the stash-users group. It is not necessary for all people e.g. in the LDAP engineering group to get a Stash license.
This is how JIRA/Confluence work, you take a license when you login for the first time and are added to the jira-users/confluence-users groups. Why is Stash behaving differently?!
The auto-add function is really great and saves a lot of waiting for enabling accounts at the same time as the number of licenses are kept optimal. Is the only solution here to maintain a separate LDAP group for those that "may" use Stash at some point?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot