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
When converting to a NONE from a LAMBDA data source, the following error is thrown during deployment.
Data source is still connected to a resolver that uses mapping template bypass. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: 3d9345df-d1ad-4d18-92e6-ac38e6dbf518; Proxy: null).
In order to get around this, the field the original LAMBDA data source was connected to must be manually deleted from the schema through the AWS console and then the original data source manually deleted from the AWS console. After doing both of these, I'm able to then deploy the NONE data source attached to the field.
The text was updated successfully, but these errors were encountered:
Leaving open since deploying shouldn't error out in this case, but it might be out of the control of this plugin (more research would be needed to find this out).
When converting to a NONE from a LAMBDA data source, the following error is thrown during deployment.
Data source is still connected to a resolver that uses mapping template bypass. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: 3d9345df-d1ad-4d18-92e6-ac38e6dbf518; Proxy: null).
In order to get around this, the field the original LAMBDA data source was connected to must be manually deleted from the schema through the AWS console and then the original data source manually deleted from the AWS console. After doing both of these, I'm able to then deploy the NONE data source attached to the field.
The text was updated successfully, but these errors were encountered: