Fix discrepancies between fv URLs across deployments and ingress (UAT/STG/PROD) #122
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
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.
What?
Edited references to FILE_VAULT_URL across deployments for PAF app and file-vault so that they all use the same URL
Also updated the file-vault ingress file so that the format matches other contemporary forms.
Why?
QAT team were unable to retrieve uploaded files in the UAT environment due to a mismatch of URLs causing incorrect redirection from filevault login, or incorrect logging of retrieval URLs causing a page not found error.
How?
Updated conditional variable declaration in deployment and ingress files.
Testing?
This will not be possible to test until it has reached UAT environment.