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
I am assuming the fail on the validation is occuring from a webhook but I am curious why we don't see the CRD pick up the required field on name but it does see it on region
Relevant Error Output Snippet
* spec: Invalid value: "object": spec.forProvider.name is a required parameter
### Crossplane Version
1.16.0
### Provider Version
1.13.0
### Kubernetes Version
1.29
### Kubernetes Distribution
Kind, EKS
### Additional Info
_No response_
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Affected Resource(s)
Resource MRs required to reproduce the bug
Steps to Reproduce
Apply this resource and see how it fails due to the
name
not being set.What happened?
Nothing in docs https://marketplace.upbound.io/providers/upbound/provider-aws-elasticache/v1.13.0/resources/elasticache.aws.upbound.io/ParameterGroup/v1beta1 or in the CRD https://github.com/crossplane-contrib/provider-upjet-aws/blob/main/package/crds/elasticache.aws.upbound.io_parametergroups.yaml#L107-L108 denotes that the name parameter should be required however in the underlying TF provider https://registry.terraform.io/providers/hashicorp/aws/5.66.0/docs/resources/elasticache_parameter_group it clearly notes that
name
is required.You can also see in TF code https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/elasticache/parameter_group.go#L62 that it does list it as required.
I am assuming the fail on the validation is occuring from a webhook but I am curious why we don't see the CRD pick up the required field on
name
but it does see it onregion
Relevant Error Output Snippet
The text was updated successfully, but these errors were encountered: