sync/allow-latest

[jdavies-st]

Resolves #1087

Allow "latest" as a CRDS file state in crds sync so that it doesn't issue a warning message for all the files it finds in this state.

There's no test for crds sync with JWST. Only HST. And the testing infrastructure here is so specialized, I'm not sure how to test this. But some pseudocode would be:

def test_sync_jwst_file_state():
    with pytest.warns() as record:
        errors = SyncScript("crds.sync some low-resource-command that reproduces warning")()
    assert errors is None
    assert len(record) is 0, record.pop().message

Tasks

• update or add relevant tests
• update relevant docstrings and / or docs/ page
• Does this PR change any API used downstream? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types)

news fragment change types...

• changes/<PR#>.hst.rst: HST reference files
• changes/<PR#>.jwst.rst: JWST reference files
• changes/<PR#>.roman.rst: Roman reference files
• changes/<PR#>.doc.rst: documentation change
• changes/<PR#>.testing.rst: change to tests or test automation
• changes/<PR#>.general.rst: infrastructure or miscellaneous change

[stscieisenhamer]

LGTM. We'll figure out some test for it. In the meantime, would you mind either 1) adding a news fragment to the jwst section or "allow edits from maintainers" on the PR.

If neither, that's ok, just let us know. Thanks!

[alphasentaurii]

Added the news fragment and made an additional adjustment related to this fix. Also modified the CI context retrieval for JWST to include the state arg "latest". Will need to do the same for other observatories once 12.x is deployed there. There are a number of tests that will need to be added and updated following those deployments so that will be done in a separate PR.