Skip to content

fix(cli): generate admin queries auth wiring #14909

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.

Sign up for GitHub

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

Merged
sharonyajain merged 2 commits into from
Sep 7, 2026
Merged

fix(cli): generate admin queries auth wiring #14909

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
20318fc
fix(cli): generate admin queries auth wiring
hariharan077 Jun 9, 2026
b78acb6
fix(cli-internal): validate admin queries migration wiring
hariharan077 Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/packages/amplify-cli/src/commands/gen2-migration/generate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,16 @@ execution. Runs last and writes `backend.ts` from accumulated content.
- **Renderers are pure.** No AWS calls, no file I/O, no `Gen1App`
dependency. Pass options, get AST nodes.

### AdminQueries REST APIs

The REST API generator recognizes the CLI-owned AdminQueries feature only when
the API resource is named `AdminQueries` and its `amplify-meta.json` entry has
the expected Cognito and Lambda dependencies. Function-name prefixes alone do
not enable AdminQueries authorization or IAM permissions. Generated Gen1 User
Pool ARNs use CDK's partition-aware `Stack.formatArn`. If the referenced Gen1
User Pool ID is missing, generation warns and scopes the Lambda policy to the
Gen2 User Pool only.

## Execution Flow

```mermaid
Expand Down
Loading
Loading