RolePolicy required field no data type, breaks things
jpoley opened this issue · 1 comments
jpoley commented
it seems like a new field is now required but doesn't have a data type here, can we please not do that.
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