Is there a way (or convention) for asserting constraints on a devcontainer feature?

[heckj]

I'm just getting into making a few features for devcontainers, and immediately got hit with a couple of requests to apply the features to very different underlying linux distributions.

So that made me wonder, first - is there a way (or even a convention) to assert a limited number of base images for which the feature is available? I'm testing against the two base images that are most important to me, but that doesn't stop someone else from trying to use it - and seeing a failure.

Second - are there any patterns developing for identifying some fundamental bits (such as base OS distribution) to help with making features cross-distribution (for example, Ubuntu, Fedora, and AmazonLinux)?

[heckj]

Related: I found some OS identification code within the features common utils, but it's not easily exposed down to clients. I've opened a feature request on that repo to expose that detail.