Repository navigation
Accept environment-qualified resource IDs across CLI workflows - #20
Merged
Merged
Conversation
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.
Environment-qualified resource IDs were rejected during enrollment and several later workflows. For example, a valid
development_agt_…response failed the CLI’sagt_-only validation after the account had already been created.Vendor the canonical resource-ID helper and use it for agent connections, screen/account validation, playlist publishing and recovery, preview/import/export, playback filters, and release input classification. Pass IDs through unchanged. Preserve unprefixed IDs, content-derived media identifiers, and separate credential validation. The contract refresh also picks up the existing BrightSign platform enum.
Validation: