Document v2 No-Code workspace metadata in the CHANGELOG - #1437
Open
galapas1 wants to merge 1 commit into
Open
Conversation
…s can find the new read fields.
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
1 participant
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.
Description
Adds a user-facing CHANGELOG note for No-Code workspace metadata that already merged in the generated v2 client via nightly OpenAPI regen (#1429). Nightly PRs are labeled no-changelog-needed; product asked for an explicit SDK note so callers can find the new read fields.
v2 workspace reads now expose:
source-module-idandno-code-upgrade-availableno-code-module-versionrelationship to a typedno-code-module-versionsresource (module-version,version-number)Omitted or null when the workspace is not No-Code. Prefer the relationship over
source-module-idNo generated code changes. Docs only.
Jira: TFECO-12943
Customer FR: FRB-7716
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.