-
Notifications
You must be signed in to change notification settings - Fork 116
Add GraphQL/REST info for uploading files to ACCS #489
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
Conversation
|
|
||
| # Upload files to Amazon S3 | ||
|
|
||
| Adobe Commerce as a Cloud Service (SaaS) supports file uploads through GraphQL mutations. This feature allows you to upload files such as images, documents, and other media to the server. Uploading files is a multi-step process, as shown in the following diagram: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I remember @jeff-matthews discouraging me from using the product name with (SaaS) after it. Jeff is this an approved usage?
Co-authored-by: Jared Hoover <98363870+jhadobe@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor changes and clarifications.
Co-authored-by: Dmytro Poperechnyy <dpoperechnyy@magento.com>
Co-authored-by: Dmytro Poperechnyy <dpoperechnyy@magento.com>
Purpose of this pull request
This pull request introduces comprehensive documentation updates to support and explain new SaaS-specific features for handling file and image uploads via Amazon S3 in Adobe Commerce's GraphQL API. The changes clarify backward-incompatible updates, provide practical usage examples for new attribute types and mutations, and expand navigation and example coverage for both GraphQL and REST APIs.
Affected pages
Links to Magento Open Source code
whatsnew
Added SaaS-specific features for using GraphQL and REST to handle file and image uploads via Amazon S3. The changes clarify backward-incompatible updates, provide practical usage examples for new attribute types and mutations, and expand navigation and example coverage for both GraphQL and REST APIs.