Infrastructure Automation with GitLab

I am looking to validate the use of devops for a team of seven people, each having a specific function.

1 Java Developer

1 System Administrator

1 Team Lead/Project Manager

1 Identity Management Admin

2 Access Management Admin

1 PKI Registration Agent

We have different workflows for each function. However, from my perspective, it's all the same. New ideas or requirements bring about new or changes to code, which initiates the workflow. To me, application updates, OS patching, and innovation are all the same. Could CI/CD pipelines be created to standardize infrastructure security and configuration as well as enable a faster and more feature tuned application release cycle? Any input would be most appreciated.

-Darryl

here are my 2 cents,

-
You can use GITLAB to have merge requests for all your security requests like adding users to the groups for every new user or existing users. the Mr can be approved by only your IAM admin. You can use GITLAB CI pipelines to go and perform the operation once the MR is approved. From the users side, the user has to provide their keys and submit as an MR so that the IAM team can validate and approve it.

-
You can deploy your applications easily using Ansible and Gitlab CI. All you need is just source code of your application and some knowledge of YAML. I am sure, your folks already are equipped with that. Ansible can be used for infra provisioning as well so you can just run the show with them. With regards to os updates, I would say ansible can easily do it. Have the SDLC workflow in place for developing playbooks and once the playbook is modularized, it can used in production.

Let me know if I answered your query and if you have any other questions.

StackExchange DevOps Q#10462, answer score: 2