You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
authIssues tied to the auth category of the CLIbugSomething isn't workingduplicateIf marked with duplicate, issue will be closed & original will be added for traceabilityplatformIssues tied to the general CLI platform
Hey @nathanthorpe 👋 thanks for raising this and for providing the workaround! It appears this is a duplicate of aws-amplify/amplify-studio#743 and more specifically, #6642. Closing in favor of tracking the existing items
josefaidt
added
bug
Something isn't working
auth
Issues tied to the auth category of the CLI
platform
Issues tied to the general CLI platform
duplicate
If marked with duplicate, issue will be closed & original will be added for traceability
labels
Sep 28, 2022
authIssues tied to the auth category of the CLIbugSomething isn't workingduplicateIf marked with duplicate, issue will be closed & original will be added for traceabilityplatformIssues tied to the general CLI platform
Before opening, please confirm:
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.17.0
Amplify CLI Version
10.0.0
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.
No manual changes made
Amplify Categories
auth
Amplify Commands
Not applicable
Describe the bug
The user pool is not being tagged by the tags.json file.
Tags.json file:
User pool:
Expected behavior
It should be tagged like the other resources
Reproduction steps
GraphQL schema(s)
Not Applicable
Project Identifier
No response
Log output
Not applicable
Additional information
Currently to get around it, in the override.ts I've been adding the following:
The text was updated successfully, but these errors were encountered: