Skip to content

ci: set up RWX administration (admins, billing, access) #24050

Open

Description

@teddyknox

Part of #24044. Blocked by #24049: this work starts only if the decision is to adopt RWX.

Before RWX can be required CI, its administration must not depend on one person.

Done when

Each of these has a recorded answer:

  • Admins. Who are the RWX organization admins? There must be more than one.
  • Vault access. Who can change which branches read each vault?
  • Emergency stop. Who suspends the RWX GitHub App if RWX must stop immediately?
  • Sign-in. Do people sign in with company SSO or with individual accounts?
  • Visibility. Who can read runs and logs? Reviewers need this to trust a check.
  • Billing. Who pays, and through which contract?
  • Vendor review. Have security and procurement approved the vendor?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

M-ciMeta: ci related work

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions