Comment 9 for bug 1334283

You can already specify a default value in the inputs schema of a SoftwareConfig resource, which I think is what you're describing as #2.

This means that the check in #1 needs to take into account the presence of a default value (which it probably will already if the validation is done in the right place)