Skip to content
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

StackSet lambdas are zipped and correctrly referenced but not uploaded during deployment #187

Open
1 task
mguja-fcc opened this issue Mar 5, 2024 · 4 comments
Labels

Comments

@mguja-fcc
Copy link

mguja-fcc commented Mar 5, 2024

Describe the bug
StackSet QM-TA-Spoke-StackSet and QM-SQ-Spoke-StackSet lambdas are zipped in cdk.out folder and s3 location correctly referred in the template but actual zip files are not uploaded into s3 buucket.

To Reproduce

  1. run npm run orgHub:deploy -- deploy quota-monitor-hub to deploy the solution
  2. Navigate to StackSet, for example, QM-TA-Spoke-StackSet and click add stack to StackSet
  3. Stack deployment fails due to error s3 kay was not found

Expected behavior
StackSet stack instances are deployed.

Please complete the following information about the solution:

  • Version: [e.g. v6.2.5]
@mguja-fcc mguja-fcc added the bug label Mar 5, 2024
@shujacks
Copy link
Member

shujacks commented Mar 5, 2024

Thanks for reaching out, we will look into this and get back with you soon.

@mguja-fcc
Copy link
Author

Any update on this ? we want to deploy though code without a need of manual steps. Thanks.

@G-Lenz
Copy link
Contributor

G-Lenz commented May 23, 2024

Just to make sure I'm understanding correctly, the stack sets won't deploy due to an s3 key error but the hub stack was deployed successfully, is that correct?

@mguja-fcc
Copy link
Author

Stackset instances won't deploy for both QM-TA-Spoke-StackSet and QM-SQ-Spoke-StackSet

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

No branches or pull requests

3 participants