chore: Stop using internal LB CNAMEs #20159
Open
Conversation
This file contains 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
Contributor
ph-One
commented
Jan 8, 2025
•
ph-One
commented
- Use proper vfs.va.gov domain name instead of internal LB CNAME for fwdproxy
- These seem to be getting used in RI's
- Use proper vfs.va.gov domain name instead of internal LB CNAME
ph-One
commented
Jan 8, 2025
config/settings/test.yml
Outdated
There was a problem hiding this comment.
Not sure that I need to change this to get RI's working
LindseySaari
previously approved these changes
Jan 8, 2025
va-vfs-bot
temporarily deployed
to
km/fwdproxy/stop-using-internal-cname/main/main
va-vfs-bot
temporarily deployed
to
km/fwdproxy/stop-using-internal-cname/main/main
LindseySaari
approved these changes
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.