Releases: semaphoreui/terraform-provider-semaphore
Releases · semaphoreui/terraform-provider-semaphore
v0.3.5
v0.3.4
Bugfixes
- Make is_default flag writable for runner resources
Full Changelog: v0.3.3...v0.3.4
v0.3.2
v0.3.1
This session added full Terraform support for SemaphoreUI runners (the agents
that execute template tasks). We added resources/data sources for global and
project runners, plus a dedicated resource to issue/rotate runner registration
tokens. This file is the human-readable release note; it follows the repo's
existing CHANGELOG.md style (release-please / Keep a Changelog).
Release notes
Features
- add
semaphoreui_runnerresource and data source for managing global (admin) runners —name,webhook,max_parallel_tasks,active, andtags, plus read-onlyis_default. Look up an existing runner byidorname. - add
semaphoreui_project_runnerresource and data source for managing project-scoped runners. Same attributes as the global runner plus a requiredproject_id. Note: project runners require a SemaphoreUI plan that permits them (the community edition returns403). - add
semaphoreui_runner_registration_tokenresource that generates and rotates the one-time registration token an unregistered runner uses to register. Works for both global and project runners (set the optionalproject_idfor project runners); change thekeepersmap to force a new token. The token is sensitive and stored in state.
Notes / behavior
- The runner resources no longer expose the registration token directly — issue it with
semaphoreui_runner_registration_token. - Generating a registration token leaves the runner inactive until it registers. When managing a runner together with a token resource, set
active = falseon the runner to avoid a perpetual diff. tagsare modeled as a set (order-insensitive), so reordering by the API doesn't produce spurious diffs.- A runner deleted outside Terraform (e.g. in the web UI) is detected as drift and planned for recreation instead of failing the plan;
destroyof an already-removed runner is a no-op.