Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,196
Community Members
 
Community Events
176
Community Groups

Configuration as Code

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

2 answers

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).

Hi, 

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

created and maintained by the community.

@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.

Like Anton Patronov likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS

Atlassian Community Events