Content editor only works when permissions are set to public

[micahwalter]

Describe the bug

It seems that when I have the permissions on a table set to public (create, read, update, delete) I am able to manage content from the admin ui without issue, but if I turn off one of those flags (create or update) I can't edit content. This seems like a big since I am logged in to the admin ui via IAM, but the auth method for my API is using just an API Key...

To Reproduce

Set your data model to "read" only. Go to the Content module and try to create or edit an item. You will get a red X error next to your item.

Expected behavior

This action should result in the content being properly updated.

Screenshots

[hsspain]

@micahwalter Thank you for this bug report. We are working on a resolution to this and will update this when it is released.

[vladimirzoyangit]

experiencing same, any updates on this?

[cwoolum]

Hello, just wanted to give an update. We are waiting for a fix to roll out the the CLI that should fix this issue.

aws-amplify/amplify-cli#7035

[micahwalter]

Hi,
Looks like this may have been fixed. Has it been released yet?

m

[cwoolum]

Yes, this should be fixed now. Can you please confirm?

[micahwalter]

yes, seems to work now. I'll close this issue...