Skip to content
New issue

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

aws-cdk-lib: Changing logical ID(human readable part) of AppSync resolver result in error upon deploy (CDK) #21350

Closed
RadoslavMarinov opened this issue Jul 28, 2022 · 2 comments
Assignees
Labels
aws-cdk-lib Related to the aws-cdk-lib package bug This issue is a bug. duplicate This issue is a duplicate.

Comments

@RadoslavMarinov
Copy link

Describe the bug

When I change the id of AppSync Resolver and deploy (cdk deploy) I receive an error

Only one resolver is allowed per field. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: fd68b0ff-38a5-4149-a797-138baf6a836c; Proxy: null

Expected Behavior

I would expect the resolver with the new ID to be attached to the GraphQL field(operation)

Current Behavior

The deploy fails with error:

Only one resolver is allowed per field. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: fd68b0ff-38a5-4149-a797-138baf6a836c; Proxy: null

Reproduction Steps

Create a new resolver

new appsync.Resolver(this.scope, "SuperResolver", {...})

then change just the id of the resolver from "SuperResolver" to "GreatResolver":

new appsync.Resolver(this.scope, "GreatResolver", {...})

and deploy.
You should get the same/similar error: Only one resolver is allowed per field

Possible Solution

No response

Additional Information/Context

Appsync library: "@aws-cdk/aws-appsync-alpha": "^2.29.1-alpha.0"
CDK library: "aws-cdk-lib": "2.29.1",

CDK CLI Version

2.29.1

Framework Version

No response

Node.js Version

16

OS

Linux Ubunty

Language

Typescript

Language Version

No response

Other information

No response

@RadoslavMarinov RadoslavMarinov added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jul 28, 2022
@github-actions github-actions bot added the aws-cdk-lib Related to the aws-cdk-lib package label Jul 28, 2022
@peterwoodworth
Copy link
Contributor

Thanks for reporting this @RadoslavMarinov,

Right now the only workaround is to remove the resolver resources, deploy that to the stack, then add them back and redeploy. We're aware of this issue and tracking it here, please bring your concerns to that thread 🙂

@peterwoodworth peterwoodworth added duplicate This issue is a duplicate. and removed needs-triage This issue or PR still needs to be triaged. labels Jul 30, 2022
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws-cdk-lib Related to the aws-cdk-lib package bug This issue is a bug. duplicate This issue is a duplicate.
Projects
None yet
Development

No branches or pull requests

3 participants