What happened?
After running the xpkg get-crds --json-schema subcommand, I realized that the metadata field is converted from:
to:
"metadata": {
"additionalProperties": false,
"type": "object"
},The additionalProperties: false is too restrictive here, and prevents using it for a YAML language server for a given rendered MR which usually has some metadata fields set (e.g. labels).
How can we reproduce it?
crossplane xpkg get-crds --json-schema crossplane.yaml in a configuration package with provider dependencies.
What environment did it happen in?
- Crossplane CLI version: 2.5.0
- Platform (e.g., linux/amd64): linux/amd64
- Crossplane version (if applicable):
What happened?
After running the
xpkg get-crds --json-schemasubcommand, I realized that themetadatafield is converted from:to:
The
additionalProperties: falseis too restrictive here, and prevents using it for a YAML language server for a given rendered MR which usually has some metadata fields set (e.g. labels).How can we reproduce it?
crossplane xpkg get-crds --json-schema crossplane.yamlin a configuration package with provider dependencies.What environment did it happen in?