Add E2E docker compose harness under tests/e2e - #24
Merged
Conversation
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
1 participant
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.
Docker compose stack for end to end integration testing during the post Plan 04 verification sprint. Brings up postgres plus limen plus forculus plus limentinus plus ostiarius plus a backend. Used to verify the full Plan 03 WG tunnel and Plan 04 proxy control plane work end to end (agent enrolls, wg0 up, ping works, ostiarius auths, route applied). Includes a short README describing test phases. Not automated yet, just a dev time harness. Closes #23