[GH-167] - Update PWS_HOST with new value from REQ7051889 #168
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.
Context: During a recent live session, we encountered an issue with the
PWS_HOST
configuration while running locally. The following was observed:PWS_HOST=https://it-wseval1.s.uw.edu
consistently resulted in500
errors.PWS_HOST=https://wseval.s.uw.edu
resolved the issue, and the application worked as expected.After doing some research I found a change that took effect in EWS EVAL environments on 5/25/23. Any configurations or bookmarks still pointing to the old endpoint will no longer work.
Change Description:
This PR updates the
PWS_HOST
value in thesettings/*.dotenv
files to reflect the current configuration for the EWS EVAL environments. The old endpointhttps://it-wseval1.s.uw.edu
consistently caused 500 errors during local testing. The new endpointhttps://wseval.s.uw.edu
resolves this issue and aligns with changes implemented on 5/25/23.For more information please refer to UW Connect's REQ7051889
Closes Github(s): GH-167
UW-Directory Pull Request checklist
poetry run tox
(Please check Side Note)semver-guidance:
label for this pull request (under labels,to the right of the screen)