-
Notifications
You must be signed in to change notification settings - Fork 121
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
Owner auth API provisioned with CLI 4.22.1 without read operation do not require owner input on subscription API #699
Comments
Possibly resolved by: #779 |
I've done some testing with the
This generates the following subscription operations within AppSync:
As we can see, the |
Describe the bug
When I provision an API with the following schema for DataStore by following these steps
operations: [create, update, delete]
. I have not restricted read permissions so all users can read each others data. The resulting subscription operations no longer require owner field as input.amplify update api
and choose enabled for DataStoreThe provisioned API have subscription operations that do not require owner field

This code is no longer correct as it will add the owner field on the subscription request and fail to create subscriptions to the API.
Previous logic that is incorrect:
Now:
Expected behavior
DataStore sync to cloud should construct the correct requests to API based on my schema. when i have a schema containing owner auth and certain operations set then it should know which subscription operations requires owner field and which do not.
Additional context
Amplify CLI related change released in 4.22.1 aws-amplify/amplify-cli#4182
iOS Issue: aws-amplify/amplify-swift#691
Android Issue: #699
JS issue: https://github.com/aws-amplify/amplify-js/issues/6507
The text was updated successfully, but these errors were encountered: