jwst/no-vars-fallback-to-latest #1106
Closed
+49
−12
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.
Resolves CCD-1540 and JP-3838
This PR addresses a bug introduced by the recent cal version-based context changes where users internal to the STScI network who have no CRDS environment variables configured are no longer able to retrieve the default context. The client will now fallback to the "latest" context if all else fails, and also default to latest if crds determines a local configuration (which occurs automatically when no server url is preset). A new test as well as a note in the relevant documentation has been added. Note - it is possible to retrieve the cached "build_context" variable but this is not necessarily reliable since the user may have updated their jwst cal version since the last crds sync took place.
Tasks
docs/pageno-changelog-entry-needed)changes/:echo "changed something" > changes/<PR#>.<changetype>.rst(see below for change types)news fragment change types...
changes/<PR#>.hst.rst: HST reference fileschanges/<PR#>.jwst.rst: JWST reference fileschanges/<PR#>.roman.rst: Roman reference fileschanges/<PR#>.doc.rst: documentation changechanges/<PR#>.testing.rst: change to tests or test automationchanges/<PR#>.general.rst: infrastructure or miscellaneous change