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

API Scheme: IAM deprecated warning, but documentation is not updated #7542

Open
2 tasks done
bergmorten opened this issue May 8, 2024 · 1 comment
Open
2 tasks done
Labels
transferred This issue was transferred from another Amplify project

Comments

@bergmorten
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

12.7.1

What operating system are you using?

windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Nope

Describe the bug

When pushing amplify we get warning that our scheme is using IAM, but this is the method which is documented at amplify website.

⚠️ WARNING: Schema is using an @auth directive with deprecated provider 'iam'. Replace 'iam' provider with 'identityPool' provider.

You need to update documentation and enum AuthProvider at e.g. https://docs.amplify.aws/gen1/javascript/build-a-backend/graphqlapi/customize-authorization-rules/#how-it-works

Expected behavior

Documentation should not use deprecated auth methods

Reproduction steps

Make a scheme like the documentation suggest and push

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@ykethan
Copy link
Contributor

ykethan commented May 8, 2024

Hey👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

@ykethan ykethan transferred this issue from aws-amplify/amplify-cli May 8, 2024
@ykethan ykethan added the transferred This issue was transferred from another Amplify project label May 8, 2024
@AnilMaktala AnilMaktala transferred this issue from aws-amplify/amplify-category-api May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
transferred This issue was transferred from another Amplify project
Projects
None yet
Development

No branches or pull requests

2 participants