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
I'm trying to create a Cognito User and AWS requests are without username field.
The User resource doc shows there is no field called username or similar.
username
I tried to use the attributes field as follows:
attributes: username = [email protected]
but I still get the AWS request error shown below: "errorMessage": "Username should be an email.",
"errorMessage": "Username should be an email.",
Try to create a Cognito User
Crossplane version: 1.17.0
Kubernetes version (use kubectl version) 1.30 Kubernetes distribution (e.g. Tectonic, GKE, OpenShift) EKS
kubectl version
The text was updated successfully, but these errors were encountered:
Any update on this?
Sorry, something went wrong.
Hi,
you want to ask that at https://github.com/crossplane-contrib/provider-upjet-aws which is the terraform based AWS provider for Crossplane. It contains all resources in *.aws.upbound.io.
*.aws.upbound.io
This is the legacy, community-maintained provider built on the AWS SDK that has the API group *.aws.crossplane.io.
*.aws.crossplane.io
No branches or pull requests
What happened?
I'm trying to create a Cognito User and AWS requests are without username field.
The User resource doc shows there is no field called
username
or similar.I tried to use the attributes field as follows:
but I still get the AWS request error shown below:
"errorMessage": "Username should be an email.",
How can we reproduce it?
Try to create a Cognito User
What environment did it happen in?
Crossplane version: 1.17.0
Kubernetes version (use
kubectl version
) 1.30Kubernetes distribution (e.g. Tectonic, GKE, OpenShift) EKS
The text was updated successfully, but these errors were encountered: