tty7

Worked a treat

Crappy example:

1 - Adding a user to a group, I expect a review - did I get the name correct?

2 - Adding a group, I expect a review & an ask - does the group make sense for our context, and is it named correctly.

Any reccomendations of how to implement this? Tags would work but only if you understand the context of ship/show/ask.

100% opening a PR, regardless if its literally just merge this badboy ends up being a "show/ask" instead of a "ship" where i am currently working

Another thing to look at is the did:peer method, it allows you to have a direct connection with a party for secure communication. Either party could root their did against a public key (eg a public organisation) but that is not required.

Just start reading the book (any discrete mathematics book!) :)

Amen

I know people don't read the article, but at least read the comment lol

it will be attacked within minutes, you should start a honeypot and see for yourselves

I'm not sure I agree the dependency on the toolchain & provider, I am always able to read what API does (vendor side) and how it has been implemented (tool side) and make a educated decision. Caveat, I do not use bleeding edge features of any cloud provider and unless engineering requires - I do not use PaaS features of cloud providers - which i find have roughest edges for infra-as-code.

Secondly I think that part of that issue is maybe that the wrong toolchain is being used. eg: Trying to use HCL (hashicorp configuration language - used in Terraform) as if its turning complete. (and i've seen this before)

I've not run into an issue where manual steps are required to cleanly deploy infrastructure which I can not automate away. I can agree on dependency chains, where you may need to run your infrastructure deployment in sequence so that eg your network is up, before you provision instances.

All this being said, I mirror my production environment in staging. So 99% issues are found there.

I think we are mostly on the same page, I just took "scared" more literally than you.

Also i would hate to be on a team who is scared to change their code, be it infrastructure or application code!

If you are scared to change your infra code then you probably are not following true infrastructure as code practises.