Test https-hosts
as part of diagnose
#7
Merged
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.
Description
This helps customers test outbound HTTPS connectivity from the main subnet. This helps assert connectivity (or not) for SSO and VCS integrations.
Related Issue(s)
Fixes ENT-630
How to test
From a private cell, w/o adding a route to send 0.0.0.0/0 over the transit gateway, run diagnose. Then add rule to the main routetable for the Gitpod VPC, and try again. It should fail the first time, and succeed the second time.
Happy path (a private cell that has a transit gateway attached, where the main subnets route 0.0.0.0/0 to it):
Sad path (I removed the routes to the transit gateway from each route table for the main subnets):
Documentation
/hold