Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

amplify env <subcommands> fails with: Found whitespace in your key name ..

See original GitHub issue

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the Amplify Console GitHub Issue Tracker

Describe the bug amplify env <subcommand> fails and leaves the following trace:

amplify env list
Found whitespace in your key name (use quotes to include) at line 22,8 >>><<<<<<< HEAD
        ...
Error: Found whitespace in your key name (use quotes to include) at line 22,8 >>><<<<<<< HEAD
        ...
    at error (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:41:11)
    at keyname (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:157:76)
    at object (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:353:15)
    at value (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:391:24)
    at object (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:358:23)
    at value (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:391:24)
    at object (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:358:23)
    at value (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:391:24)
    at object (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:358:23)
    at legacyRootValue (/Users/kjetilge/.nvm/versions/node/v14.8.0/lib/node_modules/@aws-amplify/cli/node_modules/hjson/lib/hjson-parse.js:428:38)

Amplify CLI Version 4.29.0

To Reproduce It happened the first time after I tried the following from my repos dev branch:

git checkout test
amplify env checkout test -> Error!

Expected behavior At least in the case of amplify env remove test - there should be no error.

Desktop (please complete the following information):

OS: Mac
Node Version v14.8.0

Issue Analytics

State:
Created 3 years ago
Comments:11 (3 by maintainers)

Top GitHub Comments

1reaction

SwaySwaycommented, Apr 19, 2021

@pashka4281 @paolo573 This yaml template issue looks separate then the original can you open a new issue for this? (with steps on how to repro as well)

0reactions

github-actions[bot]commented, May 24, 2021

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

Top Results From Across the Web

How to fix amplify pull issue -> local setup - Stack Overflow

I have configured the staging environment on the AWS console, and I currently am trying to setup locally on my PC. The command...

Quickstart

The Amplify Command Line Interface (CLI) is a unified toolchain to create, integrate, and manage the AWS cloud services for your app.

Project-level configurations - Command Hooks - Amplify Docs

Place your custom scripts in the amplify/hooks directory and set the script file name to the desired command with a pre or post...

Amplify CLI Cheatsheet - A.J. Bothe

A list of common commands for using Amplify CLI. ... amplify env <subcommands> add Adds a new environment to your Amplify Project pull ......

Environment variables - AWS Amplify Hosting

In the Manage variables section, under Variable, enter your key. ... section of the Amplify console with backend entered for the backend environment...