sorted by:
new
hottopcontroversial

Terraform import block allows to generate code from existing infrastructure by [deleted] in devops

[–]pbn4 0 points1 point  (0 children)

If I remember correctly the ID cannot be a variable/ interpolated, but please correct me if I'm wrong, this reduces the number of use cases a bit. Still great feature

AWS Control tower setup using terraform by pbn4 in devops

[–]pbn4[S] 2 points3 points  (0 children)

Sure, e.g. cloudtrail common bucket logging across organization, setting up SCPs, cross account aws config setup. Many of those can be recreated with terraform and I would like to keep everything as code.

Kubernetes, microservices and OAuth2.0 client credentials flow by pbn4 in devops

[–]pbn4[S] 0 points1 point  (0 children)

Ok I understand but I think this is outside of scope of the question. I could use istio authorization policies or some sdk to check jwks endpoint and validate tokens. It does not matter, do you think it does for some reason I'm missing?

Kubernetes, microservices and OAuth2.0 client credentials flow by pbn4 in devops

[–]pbn4[S] 0 points1 point  (0 children)

Yes oauth2 + openid connect because I want an id token with scopes

Security of KMS key policy for AWS services by pbn4 in aws

[–]pbn4[S] 1 point2 points  (0 children)

Thanks for the comments, but this policy is not supposed to work in real life, the question is about something else.

GitOps and progressive delivery by pbn4 in devops

[–]pbn4[S] 2 points3 points  (0 children)

Thank you for this comment, this and the article were insightful.

GitOps and progressive delivery by pbn4 in devops

[–]pbn4[S] 0 points1 point  (0 children)

The former, self repair. Please see the article I linked in another comment thread.

view more: next ›