[BUG] Backend environment cache not used

[tripproberts]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature

Backend builds

Is your feature request related to a problem? Please describe:

I have an Amplify app connected to a Github repo which consists of only backend components (Lambdas, APIs, and Auth).

On every deploy, all of my backend resources are initialized and deployed from scratch.

The below backend build logs appear in every deployment despite the env existing and many previous deployments occurring.

# Starting phase: build
# Executing command: amplifyPush -s
2024-01-19T03:45:21.489Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache
2024-01-19T03:45:21.498Z [INFO]: # Start initializing Amplify environment: tripp
# Initializing new Amplify environment: tripp (amplify init)

According to the end of the backend build step, a complete stackinfo appears to be stored in the env cache

2024-01-04T16:15:10.502Z [INFO]: # Done initializing Amplify environment: tripp
2024-01-04T16:15:10.502Z [INFO]: # Store Amplify CLI Cloud-Formation stack info in environment cache
2024-01-04T16:15:11.902Z [INFO]: STACKINFO={
                                 "awscloudformation": {
                                 "AuthRoleName": "amplify-...."
                                 .....
}

The deployment succeeds, but I'm not sure why following deployments cannot fetch stackinfo from the env cache.

My amplify.yml is pretty basic

version: 1
backend:
  phases:
    build:
      commands:
        - amplifyPush -s
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands: []
  artifacts:
    baseDirectory: docs
    files:
      - '**/*'

Describe how you'd like this feature to work

I'm expecting stackinfo to be available in the env cache for each backend deployment, and my environment updated instead of initialized each time.

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[tripproberts]

Seems to be a duplicate of #2096

I solved my issue by using a custom amplifyPush.sh script

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue has been automatically locked.