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

Bug: sam pipeline init - ResourceNotFoundException #7330

Closed
kwtsangaf opened this issue Aug 7, 2024 · 3 comments
Closed

Bug: sam pipeline init - ResourceNotFoundException #7330

kwtsangaf opened this issue Aug 7, 2024 · 3 comments
Labels
area/pipeline blocked/close-if-inactive Blocked for >14 days with no response, will be closed if still inactive after 7 days blocked/more-info-needed More info is needed from the requester. If no response in 14 days, it will become stale.

Comments

@kwtsangaf
Copy link

kwtsangaf commented Aug 7, 2024

Description:

throw out Error: An error occurred (ResourceNotFoundException) when calling the GetSecretValue operation: Secrets Manager can't find the specified secret. when running sam pipeline init --bootstrap

Steps to reproduce:

run sam pipeline init --bootstrap
image
image

Observed result:

Error: An error occurred (ResourceNotFoundException) when calling the GetSecretValue operation: Secrets Manager can't find the specified secret.
Traceback:
  File "click/core.py", line 1078, in main
  File "click/core.py", line 1688, in invoke
  File "click/core.py", line 1688, in invoke
  File "click/core.py", line 1434, in invoke
  File "click/core.py", line 783, in invoke
  File "samcli/cli/cli_config_file.py", line 347, in wrapper
  File "click/decorators.py", line 92, in new_func
  File "click/core.py", line 783, in invoke
  File "samcli/lib/telemetry/metric.py", line 185, in wrapped
  File "samcli/lib/telemetry/metric.py", line 150, in wrapped
  File "samcli/commands/_utils/command_exception_handler.py", line 89, in wrapper_command_exception_handler
  File "samcli/commands/_utils/command_exception_handler.py", line 69, in wrapper_command_exception_handler
  File "samcli/commands/pipeline/init/cli.py", line 47, in cli
  File "samcli/commands/pipeline/init/cli.py", line 56, in do_cli
  File "samcli/commands/pipeline/init/interactive_init_flow.py", line 82, in do_interactive
  File "samcli/commands/pipeline/init/interactive_init_flow.py", line 107, in _generate_from_app_pipeline_templates
  File "samcli/commands/pipeline/init/interactive_init_flow.py", line 252, in _generate_from_pipeline_template
  File "samcli/commands/pipeline/init/interactive_init_flow.py", line 192, in _prompt_run_bootstrap_within_pipeline_init
  File "samcli/commands/pipeline/bootstrap/cli.py", line 407, in do_cli
  File "samcli/lib/pipeline/bootstrap/stage.py", line 338, in bootstrap
  File "samcli/lib/pipeline/bootstrap/stage.py", line 370, in _get_pipeline_user_secret_pair
  File "botocore/client.py", line 565, in _api_call
  File "botocore/client.py", line 1017, in _make_api_call

Expected result:

should create the stack in the aws account

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

  1. OS: macOS Sonoma 14.5
  2. sam --version: 1.121.0
  3. AWS region: ca-central-1
# Paste the output of `sam --info` here
{
  "version": "1.121.0",
  "system": {
    "python": "3.8.13",
    "os": "macOS-14.5-arm64-arm-64bit"
  },
  "additional_dependencies": {
    "docker_engine": "Not available",
    "aws_cdk": "Not available",
    "terraform": "Not available"
  },
  "available_beta_feature_env_vars": [
    "SAM_CLI_BETA_FEATURES",
    "SAM_CLI_BETA_BUILD_PERFORMANCE",
    "SAM_CLI_BETA_TERRAFORM_SUPPORT",
    "SAM_CLI_BETA_RUST_CARGO_LAMBDA"
  ]
}

Add --debug flag to command you are running

@kwtsangaf kwtsangaf added the stage/needs-triage Automatically applied to new issues and PRs, indicating they haven't been looked at. label Aug 7, 2024
@mndeveci
Copy link
Contributor

mndeveci commented Aug 9, 2024

Thanks for reporting this issue.

I've tried to re-produce it on my side, however I was able to finish execution successfully. Can you provide more details about the steps you took, especially after the Summary section?

And can you also confirm that you don't have any other error messages prior to this one, which might indicate any permission issues (your credentials not having enough scope to execute the actions)?

@mndeveci mndeveci added blocked/more-info-needed More info is needed from the requester. If no response in 14 days, it will become stale. area/pipeline and removed stage/needs-triage Automatically applied to new issues and PRs, indicating they haven't been looked at. labels Aug 9, 2024
@hnnasit hnnasit added the blocked/close-if-inactive Blocked for >14 days with no response, will be closed if still inactive after 7 days label Oct 30, 2024
@mndeveci
Copy link
Contributor

Closing due to inactivity

@mndeveci mndeveci closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2024
Copy link
Contributor

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/pipeline blocked/close-if-inactive Blocked for >14 days with no response, will be closed if still inactive after 7 days blocked/more-info-needed More info is needed from the requester. If no response in 14 days, it will become stale.
Projects
None yet
Development

No branches or pull requests

3 participants