fix: (IAC-1410) Updated the default probe path #373
Merged
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
thpang
approved these changes
Apr 3, 2024
jarpat
approved these changes
Apr 3, 2024
sayeun
approved these changes
Apr 3, 2024
dhoucgitter
approved these changes
Apr 4, 2024
riragh
added a commit
that referenced
this pull request
Apr 18, 2024
jarpat
pushed a commit
that referenced
this pull request
May 17, 2024
jarpat
pushed a commit
that referenced
this pull request
Jun 28, 2024
dhoucgitter
pushed a commit
that referenced
this pull request
Aug 29, 2024
dhoucgitter
pushed a commit
that referenced
this pull request
Jan 6, 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.
Changes:
This PR updates the default probe path from
/SASLogon/apiMetato/SASLogon/loginbased on product teams recommendation.Test:
Verified Application gateway creation with default probe was successful. After deploying SAS Viya the backend health of the gateway was healthy. See detailed test result in the internal ticket.