Skip to content

feat(action): ork gate, serve play, serve apply with OIDC - #16

Open
iAlexeze wants to merge 1 commit into
mainfrom
feat/serve-gate
Open

feat(action): ork gate, serve play, serve apply with OIDC#16
iAlexeze wants to merge 1 commit into
mainfrom
feat/serve-gate

Conversation

@iAlexeze

@iAlexeze iAlexeze commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • gate — runs ork gate as an admission pre-check on a CR; no cluster needed
  • serve-play — previews a CR locally via ork serve play
  • serve-apply — applies a CR through the Gateway API; authenticates via GitHub Actions OIDC token (serve-oidc: true, no stored secret) or a static bearer token (serve-token)
  • serve-dry-run — preview mode for apply

New examples: gate-pr.yml, serve-deploy-oidc.yml, serve-full-pipeline.yml

Test plan

  • Gate step fails on a CR that would be rejected
  • serve-play prints the rendered CR without a gateway
  • serve-apply with serve-oidc: true mints a JWT and authenticates successfully
  • serve-apply with serve-token works with a static token
  • serve-dry-run: true returns without writing to the cluster
  • Missing serve-url skips the apply step cleanly
  • Missing id-token: write produces a clear error message

- gate: runs ork gate as an admission pre-check (no cluster needed)
- serve-play: previews a CR locally via ork serve play
- serve-apply: applies a CR through the Gateway API; authenticates via
  GitHub Actions OIDC token (serve-oidc: true, no stored secret) or a
  static bearer token (serve-token)
- serve-dry-run: previews apply without writing to the cluster

Adds three example workflows: gate-pr, serve-deploy-oidc, serve-full-pipeline.
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