Add custom field definitions to channel#193
Closed
caitlynstocker wants to merge 4 commits into
Closed
Conversation
caitlynstocker
commented
Apr 2, 2026
| - `field_name` (String) The name of the custom field. | ||
|
|
||
|
|
||
| <a id="nestedblock--rule"></a> |
Contributor
Author
There was a problem hiding this comment.
Autogenerated docs changes.
caitlynstocker
commented
Apr 10, 2026
|
|
||
| require ( | ||
| github.com/OctopusDeploy/go-octopusdeploy/v2 v2.105.0 | ||
| github.com/OctopusDeploy/go-octopusdeploy/v2 v2.105.1-0.20260410024644-845b3652cb8c |
Contributor
Author
There was a problem hiding this comment.
This needs to be updated to point to the latest release once changes to the go client are completed.
caitlynstocker
commented
Apr 10, 2026
| github.com/OctopusDeploy/go-octopusdeploy/v2 v2.105.0 h1:KfQngSy4tnjRfHJldIcxxE+DKeiMsJHu/1PTub/kKc8= | ||
| github.com/OctopusDeploy/go-octopusdeploy/v2 v2.105.0/go.mod h1:VkTXDoIPbwGFi5+goo1VSwFNdMVo784cVtJdKIEvfus= | ||
| github.com/OctopusDeploy/go-octopusdeploy/v2 v2.105.1-0.20260410024644-845b3652cb8c h1:6102d7f5d46u8pNkwSDQOrZSh8ACSRYOBmnOFTa7anc= | ||
| github.com/OctopusDeploy/go-octopusdeploy/v2 v2.105.1-0.20260410024644-845b3652cb8c/go.mod h1:VkTXDoIPbwGFi5+goo1VSwFNdMVo784cVtJdKIEvfus= |
Contributor
Author
There was a problem hiding this comment.
This will be removed once we are using the new release of the go client.
Contributor
Author
|
Replaced by #200 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pending advice from Modern Deployments. Please hold off on reviewing for now 🛑
Background 🌇
Custom field definitions were added to Channels as part of the Ephemeral Environments project, as a way to require custom fields on a release made into an ephemeral environment channel. The values for the custom fields on a release can then be used to name (or set other values within?) the ephemeral environments created from the release.
What's this? 🌵
We want to enable terraform users to set custom field definitions on channels in their terraform configuration.
What it should be doing so far is:
〰️ adding
CustomFieldDefinitionsto the Channel schema〰️ adding expander and flattener functions for
CustomFieldDefinitions〰️ referencing these inside the Channel expander and flattener functions.
How to review 🔍
🚩 Carefully! This is my first time touching terraform or the go client. I've checked the changes carefully but it is very much a claude special.
🧪 You can test this by creating a channel in terraform and adding, editing and removing custom field definitions. Example terraform config:
Completes DEVEX-147