Skip to content

Accept environment-qualified resource IDs across CLI workflows - #20

Merged
nxtman123 merged 1 commit into
mainfrom
fix/environment-qualified-resource-ids
Sep 17, 2026
Merged

nxtman123 merged 1 commit into
mainfrom
fix/environment-qualified-resource-ids

Conversation

@nxtman123

Copy link
Copy Markdown
Collaborator

Environment-qualified resource IDs were rejected during enrollment and several later workflows. For example, a valid development_agt_… response failed the CLI’s agt_-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:

  • 82 focused ID, encrypted-binding, playlist, and recovery tests passed, including all supported environments.
  • Typecheck, build, public/vendor checks, mock smoke, packaging, offline artifact verification, and clean npm installation passed.
  • Full suite: 698 passed, 5 failed due to missing compose fonts, 1 skipped.
  • No package publication.

@nxtman123
nxtman123 merged commit 642737b into main Sep 17, 2026
6 checks passed
@nxtman123
nxtman123 deleted the fix/environment-qualified-resource-ids branch September 17, 2026 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant