You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why i m getting profile default not be found
Run sam build --use-container
sam build --use-container
shell: /usr/bin/bash -e {0}
env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE20: true
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true
CHECK_ENV_IS_WORKING:
PIPELINE_USER_ACCESS_KEY_ID: ***
PIPELINE_USER_SECRET_ACCESS_KEY: ***
SAM_TEMPLATE: template.yml
TESTING_STACK_NAME: dev-lead-services
TESTING_PIPELINE_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-dev-pipel-PipelineExecutionRole-QZlBlRxLUQAQ
TESTING_CLOUDFORMATION_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-dev-p-CloudFormationExecutionRo-fLpHDf4da9pZ
TESTING_ARTIFACTS_BUCKET: aws-sam-cli-managed-dev-pipeline-r-artifactsbucket-mxsgyis98hth
TESTING_REGION: us-east-1
PROD_STACK_NAME: prod-lead-services
PROD_PIPELINE_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-prod-pipe-PipelineExecutionRole-3YGoaDt6exrE
PROD_CLOUDFORMATION_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-prod--CloudFormationExecutionRo-BrJgteDe53pV
PROD_ARTIFACTS_BUCKET: aws-sam-cli-managed-prod-pipeline--artifactsbucket-lnpfbifjrmhj
PROD_REGION: us-east-1
AWS_DEFAULT_REGION: us-east-1
AWS_REGION: us-east-1
AWS_ACCESS_KEY_ID: ***
AWS_SECRET_ACCESS_KEY: ***
SAM CLI now collects telemetry to better understand customer needs.
You can OPT OUT and disable telemetry collection by setting the
environment variable SAM_CLI_TELEMETRY=0 in your shell.
Thanks for your help!
Learn More: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-telemetry.html
Error: The config profile (default) could not be found
Error: Process completed with exit code 1.
The text was updated successfully, but these errors were encountered:
Why i m getting profile default not be found
Run sam build --use-container
sam build --use-container
shell: /usr/bin/bash -e {0}
env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE20: true
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true
CHECK_ENV_IS_WORKING:
PIPELINE_USER_ACCESS_KEY_ID: ***
PIPELINE_USER_SECRET_ACCESS_KEY: ***
SAM_TEMPLATE: template.yml
TESTING_STACK_NAME: dev-lead-services
TESTING_PIPELINE_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-dev-pipel-PipelineExecutionRole-QZlBlRxLUQAQ
TESTING_CLOUDFORMATION_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-dev-p-CloudFormationExecutionRo-fLpHDf4da9pZ
TESTING_ARTIFACTS_BUCKET: aws-sam-cli-managed-dev-pipeline-r-artifactsbucket-mxsgyis98hth
TESTING_REGION: us-east-1
PROD_STACK_NAME: prod-lead-services
PROD_PIPELINE_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-prod-pipe-PipelineExecutionRole-3YGoaDt6exrE
PROD_CLOUDFORMATION_EXECUTION_ROLE: arn:aws:iam:::role/aws-sam-cli-managed-prod--CloudFormationExecutionRo-BrJgteDe53pV
PROD_ARTIFACTS_BUCKET: aws-sam-cli-managed-prod-pipeline--artifactsbucket-lnpfbifjrmhj
PROD_REGION: us-east-1
AWS_DEFAULT_REGION: us-east-1
AWS_REGION: us-east-1
AWS_ACCESS_KEY_ID: ***
AWS_SECRET_ACCESS_KEY: ***
Error: The config profile (default) could not be found
Error: Process completed with exit code 1.
The text was updated successfully, but these errors were encountered: