[design]: label or filename?

[clemtibs]

Right now a type of labeling notation is used to reference configuration files, exports, and imports. The goal is to enforce a strict naming convention, but it is easy to make errors. Should the labeling system be scrapped for a more intuitive referencing of entire file/folder names?

[clemtibs]

Labels seem to be logical in use but some issues remain:

1. The name labeling has four sections, <org name>-[<custom label>|<ca heirachy label>].[ca|ee].<artifact suffix>. is assumed from env vars or the certificate itself, which seems ok for the moment. But the 2nd segment should be referenced in full. Right now, referencing it has omitted the "root" top level. This becomes troublesome when using custom names in pkictl eecert because you end up with "root" appended to a custom label which makes no sense. So, this should be changed so that referencing the second segment is done in full, including "root" so that exporting later doesn't have to assume it's presence or not.
2. Label use is documented, but not expected initially, so should full filename support should be implemented as well? The script global vars take care of paths, so what could be done first is to check if the given argument is the exact name of an actual file, if that fails, then proceed to use the label method. This is good for importing and referencing configuration, but its a little strange for referencing signing CAs. Are you referencing the config file or the folder? It's not clear. In any case, this function might be part of the full path checking in [feature]: file/path checking before it hits OpenSSL #20.