docs: document enclave ingress and egress allowlists #36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/reject-unsupported-egress"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Companion documentation for platform PR #457.
Rebased onto current docs main
6589593a40398077551b601901df389171ba6340. Current head6c4894ce8f4bc458eb840626fbb82e4bdd53fb8bis one signed commit preserving the existing author/date, changing onlydocs/reference/caution-hcl.mdanddocs/reference/deployment-configuration.md.Test plan and results
PATH=/usr/bin:/bin make build-prod IMAGE_NAME=caution-docs-pr457-cleanup— passed on the exact docs head; Zensical reported no issues.hcl::from_str::<ConfigurationFile>followed byNetworkConfig::policy()from exact platform head63f98c1676ea9a3135e934c0439f35c84b1fbbf7— all six passed.git diff --check 6589593a...HEADand clean integration with main — passed.No site deployment was performed. Coordinate publication with the platform feature; its focused deployed AWS/Nitro networking qualification remains separate from these documentation checks.
853d26c725to6c4894ce8fDocument supported on-off egress configurationto docs: document enclave ingress and egress allowlistsSuperseded by #43, the unified release documentation update. It consolidates this proposal with the other open docs updates and corrects the combined guidance against platform main
2dd613e3.Closing this PR to keep one review/release path. The original branch is retained; the replacement is not merged.
Pull request closed