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

add s3 ACL in parameter to allow different file permissions #393

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

jonmifsud
Copy link

S3 Upload facility through AppSync is missing the key ACL parameter to pass permissions. Hence any uploads which are intended to be public-read or take any other permission do not work, and the default private file mode is applied.

The changes take the ACL parameter defaulting to private and include this in the S3 request giving more control to the end user.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

marklawlor and others added 15 commits January 11, 2019 10:58
- If auto-reconnect when coming back online is needed, users should use  `client.sync` (deltaSync) instead.
add promised version as valid types for CredentialsGetter - see awslabs#264
Parity with @aws-amplify/api on graphql package dependency
…ning (awslabs#347)

Fixes awslabs#354 

This fixes an InvalidSignatureExceptions that occurs when using iamBasedAuthentication and the '@@controlEvents' variable in subscriptions
I can't find anywhere in the console that I can download a file named AppSync.js... but I have aws-exports.js.

The docs are still very confusing when new to all of these libraries that can be mixed and matched.

I can get the Amplify CLI to work out of the box, but as soon as you try to add AWSAppSyncClient instead and use the Apollo client things get very confusing to me.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants