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

running sandbox with an expired sso session prints error twice #1476

Open
josefaidt opened this issue May 8, 2024 · 1 comment
Open

running sandbox with an expired sso session prints error twice #1476

josefaidt opened this issue May 8, 2024 · 1 comment
Labels
bug Something isn't working p4 sandbox Related to the sandbox experience

Comments

@josefaidt
Copy link
Contributor

Environment information

System:
  OS: macOS 14.4.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 182.30 MB / 32.00 GB
  Shell: /opt/homebrew/bin/fish
Binaries:
  Node: 20.12.2 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/node
  Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/yarn
  npm: 10.5.0 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/npm
  pnpm: 9.1.0 - ~/Library/Caches/fnm_multishells/72748_1715201332327/bin/pnpm
NPM Packages:
  @aws-amplify/backend: 1.0.0
  @aws-amplify/backend-cli: 1.0.1
  aws-amplify: 6.2.0
  aws-cdk: 2.140.0
  aws-cdk-lib: 2.140.0
  typescript: 5.4.5
AWS environment variables:
  AWS_PROFILE = josef-gen2
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description

➜  p amplify sandbox

ampx sandbox

Starts sandbox, watch mode for Amplify backend deployments

Commands:
  ampx sandbox delete            Deletes sandbox environment
  ampx sandbox secret <command>  Manage sandbox secrets

Options:
  --debug            Print debug logs to the console
                                                [boolean] [default: false]
  --help             Show help                                   [boolean]
  --dir-to-watch     Directory to watch for file changes. All subdirectori
                     es and files will be included. Defaults to the amplif
                     y directory.                                 [string]
  --exclude          An array of paths or glob patterns to ignore. Paths c
                     an be relative or absolute and can either be files or
                      directories                                  [array]
  --identifier       An optional identifier to distinguish between differe
                     nt sandboxes. Default is the name of the system user
                     executing the process                        [string]
  --outputs-format   amplify_outputs file format
            [string] [choices: "mjs", "json", "json-mobile", "ts", "dart"]
  --outputs-version  Version of the configuration. Version 0 represents cl
                     assic amplify-cli config file amplify-configuration a
                     nd 1 represents newer config file amplify_outputs
                               [string] [choices: "0", "1"] [default: "1"]
  --outputs-out-dir  A path to directory where amplify_outputs is written.
                      If not provided defaults to current process working
                     directory.                                   [string]
  --profile          An AWS profile name.                         [string]
  --once             Execute a single sandbox deployment without watching
                     for future file changes                     [boolean]

InvalidCredentialError: Failed to load default AWS credentials
Resolution: To configure a new Amplify profile, use pnpm ampx configure profile.
Cause: Token is expired. To refresh this SSO session run 'aws sso login' with the corresponding profile.
InvalidCredentialError: Failed to load default AWS credentials
Resolution: To configure a new Amplify profile, use pnpm ampx configure profile.
Cause: Token is expired. To refresh this SSO session run 'aws sso login' with the corresponding profile.
@josefaidt josefaidt added the pending-triage Incoming issues that need categorization label May 8, 2024
@ykethan
Copy link
Contributor

ykethan commented May 9, 2024

was able to reproduce the duplicated message, marking this as bug.

@ykethan ykethan added bug Something isn't working sandbox Related to the sandbox experience p4 and removed pending-triage Incoming issues that need categorization labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working p4 sandbox Related to the sandbox experience
Projects
None yet
Development

No branches or pull requests

2 participants