Mark discrete_channel_release as deprecated as is_discrete_channel_release should be used
#122
+34
−34
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.
Background
We find an issue when we create a new project via terraform octopus provider in our CICD pipeline, because it generates unexpected value on
discrete_channel_releaseon the creation.Provider Version: OctopusDeploy/octopusdeploy - 1.1.2
Error Message:
Solution
We have both
discrete_channel_releaseandis_discrete_channel_releaseon theprojectresource, we pass the value ofis_discrete_channel_releaseto the Octopus API (mapped toDiscreteChannelReleaseproperty on the project).This PR deprecates the
discrete_channel_releaseproperty and tells users to use theis_discrete_channel_releaseinstead.[sc-128196]