Typed resources for every AWX credential type
A generic credential resource works, and it puts the whole burden of knowing what goes inside on whoever writes the terraform.
← All tags
terraform
An empty AWX instance describes an incomplete API
AWX hides POST on endpoints you have nothing to create against, so an empty instance hands back a schema that looks fine and is missing half its fields.
Generics and hooks in a generated terraform provider
Every AWX quirk used to mean another branch in a template. Now it's a field on a config struct.
AWX returns $encrypted$ and terraform stops trusting you
The most reported bug in the AWX provider was never really a bug in the provider.
Go templates as the source of a terraform provider
The AWX API describes every resource, so the provider is thirteen templates and a config file that says where the description lies.
Configuring the thing that makes tokens needs a token
The GitLab secrets engine needs a GitLab token to start, which makes provisioning it from terraform more awkward than it looks.
One provider, many AWX versions
AWX changes its API between releases, so the provider has to know which release it was generated from.
Generating a terraform provider from the AWX API
AWX describes its own resources if you send it an OPTIONS request, so writing the schemas by hand was work I did not need to do.
Writing a terraform provider for AWX
AWX has a perfectly good API, but managing it by hand stops scaling the moment more than one person touches it.