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 seems like a new field is now required but doesn't have a data type here, can we please not do that.
https://marketplace.upbound.io/providers/crossplane-contrib/provider-aws/v0.46.0/resources/iam.aws.crossplane.io/RolePolicy/v1beta1#doc:spec-forProvider-document
anything required must have a datatype, we shouldn't need to go read the go code to see. this is a bit of a mess and feels like a hack.
the upbound one calls it something different and doesn't break it https://marketplace.upbound.io/providers/upbound/provider-aws/v0.47.1/resources/iam.aws.upbound.io/RolePolicy/v1beta1
this should be visible by looking at the the spec above happens in all things running version 46
The text was updated successfully, but these errors were encountered:
https://github.com/crossplane-contrib/provider-aws/commits/master/package/crds/iam.aws.crossplane.io_rolepolicies.yaml the problem file
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
it seems like a new field is now required but doesn't have a data type here, can we please not do that.
https://marketplace.upbound.io/providers/crossplane-contrib/provider-aws/v0.46.0/resources/iam.aws.crossplane.io/RolePolicy/v1beta1#doc:spec-forProvider-document
anything required must have a datatype, we shouldn't need to go read the go code to see. this is a bit of a mess and feels like a hack.
the upbound one calls it something different and doesn't break it https://marketplace.upbound.io/providers/upbound/provider-aws/v0.47.1/resources/iam.aws.upbound.io/RolePolicy/v1beta1
this should be visible by looking at the the spec above
happens in all things running version 46
The text was updated successfully, but these errors were encountered: