Artem Volkov

03/28/2023, 5:21 PM
Hi everyone. Could you give some advice on how to organise a change management process for a Platform Team in a huge enterprise? Currently we are bootstrapping new project on a platform based on GitLab + Terraform. But there are also some change requests from dev teams. I am curious if there are some more effective way than to route them through service desk support.

Zac Rosenbauer

03/28/2023, 5:34 PM
@Artem Volkov I'm happy to discuss. Shoot me a DM and we can jump on a call.

Shon Harris

03/28/2023, 5:39 PM
That sounds like a fun project @Artem Volkov - let me know if i can be of assistance as well

Will Weiss

03/28/2023, 5:48 PM
Hi Artem ... +1 to the above. Happy to assist and provide feedback.

Andrew Boyagi

03/28/2023, 9:56 PM
Hi @Artem Volkov - are you referring to the process by which teams route their requests through to your team?


03/29/2023, 5:16 PM
@Artem Volkov If it is small project IaC then PRs is fine (extracting the module and having sensible defaults). If you don’t want to have the overhead of Tickets, give them auto deploy / destroy access limited to their environments. [roles and authorization is the tricky part] Also unsure whether you need abstraction at helm charts / terraform / application level, depending on that your solution could be simplified. Could you share more context on what each new team would need. Given that your org’s huge, you could end up building custom wrapper and exposing yaml which simplifies deployment from end user perspective. We’re building a platform (IDP) for orgs to deal with the similar issue. DM’s open, would love to chat in detail.

Kashmira Patel

04/04/2023, 5:50 PM
We have self-service for less critical resources and PRs for critical ones (think security, important storage resources, etc). gets a bit hectic for the platform team, but we started this way and are now bootstrapping an SRE team to help out with the change requests. Sticking to the PR route for critical stuff with the SRE team as well.