Skip to content

Clarify Cloud API key propagation to Namespace endpoints - #34

Open
temporal-plugin-updater[bot] wants to merge 1 commit into
mainfrom
skill-sync/2026-10-27-skill-sync-issue-148-928015a-0004
Open

temporal-plugin-updater[bot] wants to merge 1 commit into
mainfrom
skill-sync/2026-10-27-skill-sync-issue-148-928015a-0004

Conversation

@temporal-plugin-updater

Copy link
Copy Markdown
Contributor

Agents now know that API key changes reach the Namespace endpoint asynchronously, so STATE_FULFILLED or a finished temporal cloud command doesn't mean the key works yet (or has stopped working). SKILL.md adds one provider-neutral principle: save the secret before testing, retry a Namespace call with backoff before starting Workers, keep the old key during rotation until the new one passes, confirm that revocation is enforced, and check the key before an HA failover.

Upstream sources:

Draft eval PR: https://github.com/temporalio/skill-evals/pull/467

…ch the Namespace endpoint asynchronously. It covers saving the secret before testing, retrying a Namespace call with backoff before starting Workers, keeping the old key during rotation until the new key passes, confirming that revocation is enforced, and checking the key before an HA failover.
@temporal-plugin-updater
temporal-plugin-updater Bot marked this pull request as ready for review November 19, 2026 02:31
@temporal-plugin-updater
temporal-plugin-updater Bot requested a review from a team as a code owner November 19, 2026 02:31
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.

0 participants