inspect asdf_standard resources to find supported versions

[braingram]

Requires asdf-format/asdf-standard#416 (this is currently included in the CI to verify the sequence of fixes described in that PR work). This temporary change can be removed when the linked PR is merged.

This PR changes how asdf determines supported ASDF standard versions (the standard not the asdf-standard python package). With this PR asdf will inspect the asdf-standard package and support all versions that have a version-map file. This should allow asdf-standard to add new standards without breaking asdf (more on that below).

Currently if a new standard were added that contains schema changes that shouldn't require asdf code changes one would need to:

• update asdf-standard with the new version (breaking asdf tests)
• release asdf-standard (and/or add conditional logic in asdf)
• update asdf to support the new version and increase the asdf-standard lower pin
• (hopefully remember to remove the now unneeded conditional logic)

With this PR the above new standard would require no changes in asdf. This will not be true for all ASDF standard versions as some may require changes to the converters/etc where some version of the above coordination might be required.

After this PR is merged asdf-format/asdf-standard#415 can be brought out of draft.

Checklist:

• pre-commit checks ran successfully
• tests ran successfully
• for a public change, a changelog entry was added
• for a public change, documentation was updated
• for any new features, unit tests were added

[eslavich]

Should have done this a long time ago!

[eslavich]

Oops, I meant to approve before, but I must have hit the wrong button.

[eslavich]

I recommend basing this off of the manifest files, since they were meant to replace version_map-*.yml.

[braingram]

Thanks for taking a look and for this recommendation. I'm going to spend some time looking into this but will put some immediate thoughts/questions below.

One difference between the version maps and manifests is that the version maps contain entries for the file format and yaml version (see https://github.com/spacetelescope/stdatamodels/pull/253/files). Are these defined (or do they need to be defined) in the manifests?

Looking at how version map is used it determines the file format version:

asdf/asdf/_asdf.py

Line 918 in 7ae2d7e

fd.write(self.version_map["FILE_FORMAT"].encode("ascii"))

and yaml versIon:

asdf/asdf/yamlutil.py

Line 399 in 7ae2d7e

yaml_version = tuple(int(x) for x in ctx.version_map["YAML_VERSION"].split("."))

used when writing the file.

During a (albeit quick) glance over the asdf-standard tests I don't see anything that checks that the version map and manifests agree :-/

As the changes in this PR assume the version map and manifests agree (in version) I will leave this PR as draft until the above can be sorted and the tests updated.

[braingram]

Closing as the required PR asdf-format/asdf-standard#415 was closed.

It may be worth revisiting this in the future but at the moment this isn't ready for "prime time".