You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I wrote a short Python script to read in all of the YAML files in the project for the purposes of verifying content, like what extensions are referenced, but never defined. The specific YAML files that reference extensions are (at least) instructions, extensions, CSRs, and profiles. The first three have a "kind" field identifying what each YAML represents, but the latter, "profiles", does not. Current "kind" fields are:
Describe the solution you'd like
I'd like to see the YAML files describing profiles also have a kind field like:
kind: profile
Describe alternatives you've considered
It's actually difficult to work around, because the top-level field is a profile name, so not a consistent key that can be checked for existence.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I wrote a short Python script to read in all of the YAML files in the project for the purposes of verifying content, like what extensions are referenced, but never defined. The specific YAML files that reference extensions are (at least) instructions, extensions, CSRs, and profiles. The first three have a "kind" field identifying what each YAML represents, but the latter, "profiles", does not. Current "kind" fields are:
Describe the solution you'd like
I'd like to see the YAML files describing profiles also have a kind field like:
Describe alternatives you've considered
It's actually difficult to work around, because the top-level field is a profile name, so not a consistent key that can be checked for existence.
The text was updated successfully, but these errors were encountered: