Skip to content

Run current OATS consumer suites#1180

Draft
zeitlinger wants to merge 1 commit into
open-telemetry:mainfrom
zeitlinger:gregor/oats-current-consumer
Draft

Run current OATS consumer suites#1180
zeitlinger wants to merge 1 commit into
open-telemetry:mainfrom
zeitlinger:gregor/oats-current-consumer

Conversation

@zeitlinger

Copy link
Copy Markdown
Member

Summary

  • replace the legacy direct OATS invocation with the current CLI config plus root oats.toml
  • convert the existing compose and k8s example suites to the current OATS schema
  • run them through a gcx wrapper so consumer CI exercises the current OATS path

Why

This gives the current OATS implementation real downstream CI coverage for:

  • compose-backed app suites
  • k3d / kubernetes-backed app suites
  • trace assertions with match_spans
  • structured log assertions with regex attribute matching

Validation

  • /tmp/oats --config oats.toml --list
  • CI will run mise run oats-tests on this branch using the current OATS CLI

@zeitlinger zeitlinger requested review from a team as code owners June 17, 2026 10:10
@zeitlinger

Copy link
Copy Markdown
Member Author

This PR switches the consumer suites onto the current OATS CLI, but I am not seeing any GitHub Actions runs for the PR head yet (only EasyCLA). Could a maintainer enable/approve Actions for this fork PR so we can get real consumer CI validation of the compose and k3d cases?

@zeitlinger

Copy link
Copy Markdown
Member Author

Temporarily closing to retrigger PR workflows on the latest consumer-validation head; reopening immediately.

@zeitlinger zeitlinger closed this Jun 17, 2026
@zeitlinger zeitlinger reopened this Jun 17, 2026
@zeitlinger zeitlinger marked this pull request as draft June 17, 2026 11:13
@zeitlinger

Copy link
Copy Markdown
Member Author

I reproduced the merge conflict locally and resolved it against current main, but publishing the rebased branch is blocked by GitHub workflow-file permissions: rebasing onto current main pulls in upstream workflow changes, and PAT-based force-push is rejected without workflow scope. If a maintainer can use GitHub's Update branch button or rebase this draft branch from a workflow-write-capable checkout, the current-OATS consumer changes themselves are already resolved locally.

@zeitlinger zeitlinger force-pushed the gregor/oats-current-consumer branch from d716210 to abbfd9b Compare June 22, 2026 11:54

Copy link
Copy Markdown
Member Author

I pushed two follow-up commits on June 25, 2026 to retrigger CI on the fixed YAML head (6cc0c5a9954df91d8ab573a727426248c0568381), but the PR still only shows EasyCLA and no GitHub Actions runs for the new head. The previous OATS rerun that failed was still on the old commit (abbfd9b...).

Could a maintainer please approve/enable Actions for the current fork PR head so the refreshed OATS Tests run on 6cc0c5a...? That is the remaining piece of real validation on this consumer PR.

@zeitlinger zeitlinger force-pushed the gregor/oats-current-consumer branch 3 times, most recently from 62a1a72 to 24fdb7f Compare June 25, 2026 13:56
Signed-off-by: Gregor Zeitlinger <[email protected]>
@zeitlinger zeitlinger force-pushed the gregor/oats-current-consumer branch from 24fdb7f to c73b9d9 Compare June 25, 2026 13:58
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