Repository navigation
Clarify Cloud API key propagation to Namespace endpoints - #34
Open
temporal-plugin-updater[bot] wants to merge 1 commit into
Open
temporal-plugin-updater[bot] wants to merge 1 commit into
temporal-plugin-updater[bot] wants to merge 1 commit into
Conversation
…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.
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.
Agents now know that API key changes reach the Namespace endpoint asynchronously, so
STATE_FULFILLEDor a finishedtemporal cloudcommand 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