This repository was archived by the owner on Jul 22, 2025. It is now read-only.
Add new resource for managing project in-built package release triggers #919
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[sc-116756]
Fixes OctopusDeploy/Issues#9483.
It is currently possible to get a project into a broken state via the API by enabling ARC without an associated package. The current provider implementation can reach this state due to the chicken-and-egg problem of requiring a package used by an existing process step in order to specify an ARC strategy. As no process steps can exist until a project is created, the project can end up in a state where ARC is enabled without any associated package reference, causing unexpected null reference exceptions when navigating the UI.
This introduces a new
auto_create_releaseresource which replaces project resource attributesauto_create_releaseandrelease_creation_strategy. The new resource has a dependency on the project, preventing users from getting into a broken state by enforcing an order of operations that requires the project to be created before ARC is enabled.