Document connected rollout and runtime account permissions - #59
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
2 participants
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.
The shared-account documentation still described unmerged companion patches, expired Google credentials and an undeployed integration. It now records the merged Cosift/auth/MCP/installer PRs, successful signed v0.2.7 release and public gateway cutover, production Cloud Run origins/revisions, public v0.4.0/v1 installer, and verified real email/shared-account checks. The original v0.2.5 status is identified as the retained rollback baseline.
The documents distinguish completed engine readiness, retrieval comparison, moderation, public cutover and local-artifact indexing from the remaining final public-client checks, long-lived credential refresh, and unfinished article authoring/view rewards. Stripe remains pending its API key, webhook secret and payment checks. Historical patch reproduction instructions now warn against reapplying changes already on companion main branches.
Includes the existing minimal community account IAM role definition: database metadata, entity read/query/update; no create/delete permissions. No runtime code or deployment workflow changes.
Validation: YAML parsed successfully; role file matches the existing operator artifact byte-for-byte; all 10 relative documentation links resolve;
git diff --checkpasses. Deployment claims were checked against GitHub merge/release records, unauthenticated production health probes, and the agents performing live rollout checks.