terraform-provider-circleci
terraform-provider-circleci copied to clipboard
mrolla
Add a provider for scheduled pipelines
This works structurally mostly like environment variables, but uses schedule IDs as internal IDs.
Some hackery has been performed to make organization ID inheritance from provider settings work. It does work correctly for the most part, though local state can get a bit confused if the provider setting gets changed. Explicit organizations on schedules work just fine though.
The scheduled actor ID in this is one of several magic IDs that we have at CircleCI, and I can guarantee to remain stable.
CRUD operations have been verified to work off the local tree, and import of existing schedules works as well.
Some provider-side validation is being performed, though it's much easier to just let the operation fail and print out the API error message, rather than duplicating all validation we perform in the API here. An example here is the project<>schedule-name uniqueness constraint, which is not checked in the provider. Similarly the requirement for either a branch or tag to be set as part of parameters, which is actually due to change soon.
Fixes #59.
On Wed, 31 Aug 2022, at 22:35, Mark Johnson wrote:
Would love to see support for scheduled pipelines. Any ETA on this?
This currently depends on @mrolla. We have been thinking about publishing an official terraform provider as well, but we’re still in a discovery phase on that, so that might take a while.