terraform-provider-spotify
terraform-provider-spotify copied to clipboard
conradludgate
But why?
For a more detailed answer, since a lot of people have asked:
I had been using terraform for a couple months. I found the terraform-provider-aws docs to be kinda disappointing so I frequented the codebase to see how it handled the data I provided.
From there, I got familiar with the CRUD style interface that terraform provides, and decided to implement one myself. I had already been familiar with Spotify as a fairly large API that I could try to wrap, so that was a natural choice for me to pick.
Nice one, might be good to throw in the top of the readme as a bit of an intro
I found the terraform-provider-aws docs to be kinda disappointing
We're always looking for ideas on ways to improve. If you have some themes, let us know!
@YakDriver I am now full time GCP engineer, and found with the AWS docs, there was a clear lack of examples talking about the code that you'd just told us how to use.
Take load balancing K8's
https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html - very in your face, so many words
https://cloud.google.com/kubernetes-engine/docs/concepts/ingress - explains what you're doing and why, then gives the code examples.
