aws-amplify / aws-amplify/amplify-cli

Each time I publish I get a "additional security enhancement" prompt...

Open
#11,108 6 comments 0 reactions 0 assignees View on GitHub
bug hosting p2 platform regression
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### How did you install the Amplify CLI?

nom

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

16.16.0

### Amplify CLI Version

10.2.1

### What operating system are you using?

Mac

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

No

### Amplify Categories

api

### Amplify Commands

publish, push

### Describe the bug

Every time I publish I get the following warning:

This version of Amplify CLI introduces additional security enhancements for your GraphQL API. The changes are applied automatically with this deployment. This change won't impact your client code. Continue?

Then it seems to do a full push, even if nothing has changed...

### Expected behavior

I should be able to publish without the entire environment needing to be pushed...

### Reproduction steps

amplify publish

### GraphQL schema(s)

_No response_

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the behavior with Amplify CLI 10.2.1 on macOS using Node.js 16.16.0 and the reported `amplify publish` command. Trace why an unchanged GraphQL API triggers the security-enhancement prompt and a full push; done means repeated publishes avoid both when no resources have changed.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, graphql, node.js, typescript
Domain
api, cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.