Skip to content

Add bidirectional probes to egress policy example - #57

Merged
BDev-Koyeb merged 1 commit into
mainfrom
test/egress-bidirectional-probes
Aug 4, 2026
Merged

Add bidirectional probes to egress policy example#57
BDev-Koyeb merged 1 commit into
mainfrom
test/egress-bidirectional-probes

Conversation

@BDev-Koyeb

Copy link
Copy Markdown
Contributor

The original example only proved the blocking direction (block_network=True → request fails). It never verified that an allowlist actually permits the listed destinations, or that resetting to default restores connectivity.

Add probes that exercise both directions:

  • After allowlist update, confirm 1.1.1.1 (allowlisted) is reachable while example.com (not allowlisted) is still blocked.
  • After reset to default, confirm public internet is reachable again.

Also factor out assert_blocked/assert_allowed helpers for clarity.

Generated by Mistral Vibe.

The original example only proved the blocking direction (block_network=True
→ request fails). It never verified that an allowlist actually permits
the listed destinations, or that resetting to default restores
connectivity.

Add probes that exercise both directions:
- After allowlist update, confirm 1.1.1.1 (allowlisted) is reachable
  while example.com (not allowlisted) is still blocked.
- After reset to default, confirm public internet is reachable again.

Also factor out assert_blocked/assert_allowed helpers for clarity.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
@BDev-Koyeb
BDev-Koyeb merged commit 0c07a40 into main Aug 4, 2026
10 checks passed
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.

2 participants