Update lastModified For Stacks/Samples Without Versions about api HOT 3 CLOSED

Started looking into this issue. I noticed when trying to run generate_last_mod_file.sh when there are samples present that don't have versions it will error out as the JSON parsing can't find the versions key. For reference about samples that don't have versions I was using the ones from registry-support tests and also noticed there is no revision.

This got me thinking about how we want to go about this, since for some of these yaml fields it isn't necessary we would need to have support for building all different combinations. I know our community registry will all have versions and revision but for others hosting their own registries do we want to accommodate every combination or have it up to their discretion to alter it?

wdyt @michael-valdron @thepetk

With our current format I think is necessary to support all combinations. The registry-support tests should also make sure of this (so we should have sufficient test cases). TBH I don't have a strong opinion if we should make a convention that the last modified field should be used only for versioned stacks/samples, although in that case we should make sure that our documentation makes it clear.

Slightly different scope, but your point makes me think of registry versioning. Meaning, if we had a versioning for the registry repo and a proper release process, for issues like that we could just create a new major version which introduces breaking changes.

from api.

Related issue: #1327

from api.

Started looking into this issue. I noticed when trying to run generate_last_mod_file.sh when there are samples present that don't have versions it will error out as the JSON parsing can't find the versions key. For reference about samples that don't have versions I was using the ones from registry-support tests and also noticed there is no revision.

This got me thinking about how we want to go about this, since for some of these yaml fields it isn't necessary we would need to have support for building all different combinations. I know our community registry will all have versions and revision but for others hosting their own registries do we want to accommodate every combination or have it up to their discretion to alter it?

wdyt @michael-valdron @thepetk

from api.