Skip to content

refactor(antithesis): Reorganization of antithesis tooling - #26038

Open
graphcareful wants to merge 7 commits into
masterfrom
chore/consolidate-antithesis-code
Open

refactor(antithesis): Reorganization of antithesis tooling#26038
graphcareful wants to merge 7 commits into
masterfrom
chore/consolidate-antithesis-code

Conversation

@graphcareful

@graphcareful graphcareful commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

Reorganizes some of the antithesis tooling to enable re-use of items such as dockerfiles and core shared test components such as the oracle.

Vector configuration

No change to Vector itself.

How did you test this PR?

Running some of the existing antithesis runs to ensure they run to completion.

Is this a breaking change?

  • Yes
  • No

Does this PR include user facing changes?

  • Yes. Please add a changelog fragment based on our guidelines.
  • No. A maintainer will apply the no-changelog label to this PR.

References

Notes

  • Please read our Vector contributor resources.
  • Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
  • Some CI checks run only after we manually approve them.
    • We recommend adding a pre-push hook, please see this template.
    • Alternatively, we recommend running the following locally before pushing to the remote branch:
      • make fmt
      • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
      • make test
  • After a review is requested, please avoid force pushes to help us review incrementally.
    • Feel free to push as many commits as you want. They will be squashed into one before merging.
    • For example, you can run git merge origin master and git push.
  • If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
    run make build-licenses to regenerate the license inventory and commit the changes (if any). More details on the dd-rust-license-tool.

@graphcareful
graphcareful requested review from a team as code owners August 5, 2026 20:40
@graphcareful
graphcareful requested a review from blt August 6, 2026 19:47
@graphcareful graphcareful added the no-changelog Changes in this PR do not need user-facing explanations in the release changelog label Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog Changes in this PR do not need user-facing explanations in the release changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant