amplify build is breaking backend override #11791
Comments
|
Hey @JefStat 👋 thanks for raising this! As we begin to look into this a bit further would you mind sharing the affected override for |
josefaidt
added
platform
|
sure just the override ts? override.ts |
github-actions
bot
removed
the
pending-response
|
Running |
|
Hey @JefStat thanks for posting that! While I don't see anything that immediately stands out in the posted override code, can you try re-running that command with the |
josefaidt
added
the
pending-response
|
First time running build nothing the second time |
github-actions
bot
removed
the
pending-response
|
I have the exact same issue. Can you please advise regarding the resolution timeline? |
|
i am also seeing this same issue. my |
|
This won't be very helpful but after trying to debug this issue by running it from the amplify cli source it resolved itself. Supposing the issue is a problem with the host machine I'm using, another change was I had recently updated OSX to Ventura. |
|
mmm, i also recently update to Ventura (macOS 13.1). |
|
Hey @JefStat and @acusti I was able to reproduce an issue if my override is attempting to reference a resource resources.addCfnParameter(
{
type: 'String',
description:
'The id of an existing User Pool to connect. If this is changed, a user pool will not be created for you.',
default: 'NONE',
},
'AuthCognitoUserPoolId',
{ 'Fn::GetAtt': ['117236f41090f', 'Outputs.UserPoolId'] }
)Here, although my resource is named When this override fails to package the push attempt flashes with an error and quickly proceeds to the CFN update without actually kicking off the CFN update. This causes the CLI to hang indefinitely and requires manually cancelling out of the flow (as described in #11607) Can you verify the resource references use the correct resource name, and confirm whether auth also has an override applied? Despite this, I am not able to reproduce the issue where subsequent |
josefaidt
added
the
pending-response
|
the
i do not have any overrides applied to auth. the REST API override is the only one in my entire application. |
|
The issue is resolved after upgrading MacOS Ventura to 13.2 (22D49) |
|
Hey folks apologies for the delay here but I wanted to follow up. Are you still experiencing this with the latest version of Amplify CLI (10.7.3)? Are there any custom resources in the project that are depending on the |
|
Hey @JefStat and folks in the thread, are you still experiencing this issue? |
|
I'm past this issue ty. |
github-actions
bot
removed
the
pending-response
|
|
@josefaidt in my app, my real issue was #11851, so i’m not having issues anymore since upgrading the CLI |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.18.1
Amplify CLI Version
10.6.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 manual changes made
Describe the bug
It's been 2 months since I last deployed or touched my amplify project. Getting back to it today to add analytics I couldn't deploy due to errors.
I updated the amplify cli to latest but I'm not sure what version I updated from.
Expected behavior
I expect amplify build not to break subsequent builds
Reproduction steps
error
Failed to override pccapi due to: InvalidOverrideError: Packaging overrides failed..Project Identifier
729269ed0dfa7238ed8a5b3b8f9c5f9a
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: