Skip to content

failed build - using latest version which is in a failed state. #151

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.

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

Open
rdyar opened this issue Jan 10, 2021 · 6 comments
Open

failed build - using latest version which is in a failed state. #151

rdyar opened this issue Jan 10, 2021 · 6 comments

Comments

@rdyar
Copy link

rdyar commented Jan 10, 2021

went to deploy a project and it failed, traced it back to this plugin which is currently in a failed state. We were pulling in the latest version so it is now pinned to the previous version in our package.json file like:

"serverless-plugin-split-stacks": "1.9.3"

@ghost
Copy link

ghost commented Jan 11, 2021

hi @rdyar, may I ask how you traced the problem?

@gusfune
Copy link

gusfune commented Jan 11, 2021

I had the same issue here. After rolling back to 1.9.3 it went back to work. It seems the resource template generated for CloudFormation is invalid.

@rdyar
Copy link
Author

rdyar commented Jan 11, 2021

the error said Template format error: Unresolved resource dependencies [ApiGatewayResourceAppAnyVar], I searched my project for ApiGatewayResourceAppAnyVar and got nothing, then the error said what the cloud formation template file was named and its path so I downloaded that and found that string in there, then I compared a previous good template, it had the same string, then I noticed in front of the good one it was part of a nested stack, the new bad one did not say that.

Then checked the npm site for this module and saw it was in a failed state.

@BrunoAPazetti
Copy link

Have the same here, going back to 1.9.3 my project works

@tvb
Copy link

tvb commented Jan 12, 2021

I've been pulling my hair out for two days because of this "Unresolved dependencies" error. If only I noticed the version bump of this plugin... dang

@tvb
Copy link

tvb commented Jan 12, 2021

Duplicate of #149

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants