Configuration as Code

[Steve Cocks]

Hi

We are moving heavily into automation and have literally hundreds of teams and 1000's of developers. We get many requests on a daily basis to change a variety of settings in BitBucket projects, Jira projects and Confluence Spaces. We have full time dedicated admins who handle all this work using tickets and manual work but this is obviously not an ideal situation

We would like to introduce "Configuration as Code" across all our tooling (not just Atlasian products) as well as for things like access management and networking (all again being done by hand today)

We are looking at using Jenkins pipelines to read yaml files that contain all our tooling configurations that can be updated wither through pull requests or self service portals

Has anybody had any experience of doing this? Are there any good patterns we should be following or pitfalls to be aware of? 

Would hate to spend a lot of time perfecting something that has already been done or abandoned as being unfeasible.

Also does anybody know if the various REST API's Atlassian supply cover everything that we need to do to administer the teams. In particular CRUD for each of the following

• BitBucket projects
• Jira projects, custom fields, screens, workflows
• Confluence spaces

Thanks

Steve

[Nick Pan]

There appears to be at least one limitation in the Jira REST API - cannot create association between Screen and Workflow Transition (but can read them).

[Peter Jans]

Hi, 

Did you perhaps already have had a look at Terraform, and the different providers:

• Jira - https://github.com/fourplusone/terraform-provider-jira
• Confluence - https://github.com/chesshacker/terraform-provider-confluence
• ButBucket - https://github.com/aeirola/terraform-provider-bitbucket

created and maintained by the community.

[Ruslan Lutsenko]

@Peter Jans thanks for the suggestion as you can see ButBucket provider is just fork from inactive repo which was republished to Terraform registry and it's missing support and missing quite a number of resources:

Missing resources are:

branch restrictions
teams (members, projects, permissions, ...)
user members
pipelines / pipeline configs

Would be so much better if Atlassian become an owner and provide support for these Terraform modules which is suggested in https://jira.atlassian.com/browse/BCLOUD-17209 
With 2000+ repos and hundreds of teams in organisation it's really problematic to maintain Bitbucket without proper automation tool.