Using Terraform & AWS CodePipeline to spin up a licensed BitBucket DC. We have all working except licensing. We host a "bitbucket.properties.tpl" to create the bitbucket.properties file containing a valid license, however, we're still prompted to enter license info when the service has been span up - yet the bitbucket.properties file exists and contains all relevant information with the exception of:
# setup.displayName removed by unattended setup on YYYY-MM-DDTHH:MM:SS.XXXZ # setup.baseUrl removed by unattended setup on YYYY-MM-DDTHH:MM:SS.XXXZ
Entering the same license info via the GUI & specifying the initial user removes the comments from the file, and that's about it for the bitbucket.properties file. The other EC2 instance in another AZ does not have its bitbucket.properties file updated, though Hazelcast port is open.
We used the same approach when spinning up BitBucket Server (i.e. *not* Data Center) and were not prompted to enter license information.
So ... Atlassian support suggested we reach out to the community while we're undergoing proof of concept/evaluation.
Has anyone automated the deployment of BitBucket DC using Terraform and AWS CodeDeploy? If so, how did you overcome automating licensing?
One option would be to pre-bake a licensed AMI, but this feels a bit of a hack.
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events