#chatops (2020-05)

Automation using Chat Bots with systems like Slack and GitHub Archive: https://archive.sweetops.com/chatops/

2020-05-14

2020-05-13

sheldonh avatar
sheldonh

Here’s something to pose… Might be partially a DevOps question and partially a chat ops.

So Netflix supposedly allows creation of repos through chat ops. I really like the concept as it reduces a lot of barrier to getting stuff done quickly.

However how do we balance this in a infrastructure as code type of world?

So there’s a lot of quick automation things I could do such as say create a repo, set up an alert for a cloud watch alarm etc. But if you are using infrastructure as code should the barrier be allow somebody to do it in chatops or something instead that maintains state like terraform and requires committing to that approach?

To me they seem slightly at odds.  The world of chatops, runbooks, and iac plans all cross over in many areas so curious how you think about this.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Yea, there’s sometime a conflict like you describe

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

I would like chat ops for this too, but in that case, it’s really more about the bot then creating a PR.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Then what does the process look like? is there CR, etc. Don’t have the answer.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

I think one is traded for the other.

sheldonh avatar
sheldonh

Got ya. Different approaches. Good to know someone else observes that. If it doesn’t get in the way maybe cut offs can be a better option. If you need the ability to easily tear down and manage things across multiple environments maybe that’s where the infrastructure is superior.

sheldonh avatar
sheldonh

So my scenario it would make perfect sense to not worry about provisioning a new GitHub repo through terraform if you don’t need the ability to centralize the policies applied and all

    keyboard_arrow_up