generated from amazon-archives/__template_DevGuide
-
Notifications
You must be signed in to change notification settings - Fork 289
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Describe the bug
If i use the script stage_solution.sh with the parameter solution-directory the layer_code folder is muissing.
To Reproduce
Steps to reproduce the behavior:
- Try to execute:
./sra/utils/packaging_scripts/stage_solution.sh --solution_directory $CURRENT_FOLDER/sra/solutions/guardduty/guardduty_org --staging_bucket_name "sra-staging-$AWS_ACCOUNT-eu-central-1" $WITH_PROFILE
- It will not call the function:
package_and_stage_solutions
instead this functionpackage_and_stage_common_solutions
will be called, which is depends on the following if:if [ "$solution_directory" != "none" ]; then
Expected behavior
Even if we pass the parameter solution-directory that the folder layer_code is created.
Additional context
The executed code block:
https://github.com/aws-samples/aws-security-reference-architecture-examples/blob/main/aws_sra_examples/utils/packaging_scripts/stage_solution.sh#L401C1-L430C3
mlfulleraws
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working