We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's hard to figure out which CRD they can reference or select just by looking at the field name
We can add type name to field doc when we add these fields to the struct.
The text was updated successfully, but these errors were encountered:
I think we now have this documentation in the generated OpenAPI v3 schema. An examplehttps://github.com/upbound/provider-aws/blob/main/package/crds/kinesis.aws.upbound.io_streamconsumers.yaml#L116C59-L116C59 is:
Sorry, something went wrong.
No branches or pull requests
What problem are you facing?
It's hard to figure out which CRD they can reference or select just by looking at the field name
How could Terrajet help solve your problem?
We can add type name to field doc when we add these fields to the struct.
The text was updated successfully, but these errors were encountered: