unable to initialize project with auth from git, missing `auth/.../build/parameters.json` #9508

josefaidt · 2022-01-12T21:04:57Z

Before opening, please confirm:

I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
I have searched for duplicate or closed issues.
I have read the guide for submitting bug reports.
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?

pnpm

If applicable, what version of Node.js are you using?

16.13.1

Amplify CLI Version

7.6.8

What operating system are you using?

mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Amplify Categories

auth

Amplify Commands

init

Describe the bug

Unable to initialize new environment from an Amplify project after freshly cloning from git due to missing parameters.json in the auth resource's build/ directory. As a workaround, we can run amplify build to generate the missing file and allow us to initialize an environment.

Note: we are also unable to use the --app parameter of init to initialize a project from git:
amplify init --app git@github.com:josefaidt/missingauth.git

✔ Successfully created initial AWS cloud resources for deployments.
✔ Initialized provider successfully.
✖ There was an error initializing your environment.
Error: File at path: '/Users/josef/Documents/projects/aws-amplify/reproductions/missingauth2/amplify/backend/auth/missingauthbf3f264f/build/parameters.json' does not exist
at Function.JSONUtilities.readJson (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/amplify-cli-core@2.4.7/node_modules/amplify-cli-core/src/jsonUtilities.ts:25:15)
    at StateManager.getData (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/amplify-cli-core@2.4.7/node_modules/amplify-cli-core/src/state-manager/stateManager.ts:399:32)
    at StateManager.getResourceParametersJson (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/amplify-cli-core@2.4.7/node_modules/amplify-cli-core/src/state-manager/stateManager.ts:147:17)
    at ensureAmplifyMetaFrontendConfig (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/on-category-outputs-change.ts:84:55)
    at AmplifyToolkit.onCategoryOutputsChange [as _onCategoryOutputsChange] (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/on-category-outputs-change.ts:18:5)
    at initializeEnv (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/initialize-env.ts:103:27)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onSuccess (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/init-steps/s9-onSuccess.ts:68:3)
    at Object.run (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/commands/init.ts:30:7)
    at Object.executeAmplifyCommand (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/index.ts:373:5)
    at executePluginModuleCommand (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/execution-manager.ts:178:3)
    at executeCommand (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/execution-manager.ts:30:5)
    at Object.run (/Users/josef/.fnm/node-versions/v16.13.1/installation/pnpm-global/5/node_modules/.pnpm/@aws-amplify+cli@7.6.8/node_modules/@aws-amplify/cli/src/index.ts:205:5)

Expected behavior

New or existing environment is initialized

Reproduction steps

amplify init -y
amplify add auth > choose defaults with username
amplify push -y
add to git (sample: https://github.com/josefaidt/missingauth.git)
cd to an empty sibling directory, mkdir ../missingauthtmp; cd ../missingauthtmp
clone from git git clone git@github.com:josefaidt/missingauth.git
attempt to initialize the project with amplify init > create new environment
observe error

Workaround

run amplify build
observe resource build directory is created and populated
initialize with amplify init

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information

No response

The text was updated successfully, but these errors were encountered:

stevenlafl · 2022-01-23T05:36:32Z

+1 Having the same problem. Same service, auth.

Edit: This worked for me:

Pull down the code as says in the Amplify Studio "Local setup instructions" section. (the amplify pull command)
Copy out the amplify/team-provider-info.json file into your existing code location.
Run amplify init
Run amplify push

Seems to provision the correct resources. 3 and 4 should happen automatically if you push the code into your git repository, according to docs. However I have not tested that.

adi518 · 2022-02-06T18:17:16Z

Getting the exact same bug. Unacceptable. Our preview builds don't work because of this. The workaround didn't work either, nor do I see how it should help. I already pulled the environment and pushed whatever updates it had to the branch I'm building an environment from.

Leandros · 2022-02-09T09:59:24Z

Same issue here. Our entire auth stack is gone.

swaminator · 2022-02-14T21:51:50Z

@Leandros @adi518 can you please provide repro steps?

adi518 · 2022-02-14T22:15:41Z

Build a preview environment with the latest major version of the cli and it should fail when using a social auth provider (e.g., Google). I finally managed to work around it today by tapping into the Amplify config before it starts creating the environment and removing any social providers, so it skips the problem altogether. I should say this pipeline used to work fine with a much older version of the cli. However, since the sabotage in colors.js, the cli had to be inevitably upgraded to the latest (the sabotage was purposely released as a patch), which lead to these new regressions when deploying a preview environment.

phaedonmit · 2022-03-17T23:51:01Z

Is there a recommended fix for this?

danshev · 2022-03-20T15:07:20Z

Same -- does anyone from AWS ever respond?

amplify remove auth >> menu of stuff to delete

amplify update auth >> build/parameters.json' does not exist

may215 · 2022-04-07T09:57:20Z

I have the same issue here? Any updates??

InnovateWithEric · 2022-04-12T16:52:43Z

This is fixed in 8.0.1 @may215

duranmla · 2022-10-19T08:18:34Z

I'm having this issue on the CI, wonder how to deal with this if the build is something that runs on the CI. 🤔

duranmla · 2022-10-19T08:51:25Z

Just FYI @josefaidt if worth something, I had this problem with amplify CLI 10.3.0, I try to update the auth resource but it didn't work so I went to build settings and change to amplify 10.2.3 and it worked, perhaps this latest version is introducing an issue.

Project Identifier: 7c991c00dbf89c25ef50f4c169fe031e

WebManifestation · 2022-10-19T10:41:26Z

Just FYI @josefaidt if worth something, I had this problem with amplify CLI 10.3.0, I try to update the auth resource but it didn't work so I went to build settings and change to amplify 10.2.3 and it worked, perhaps this latest version is introducing an issue.

Project Identifier: 7c991c00dbf89c25ef50f4c169fe031e

Thanks, this worked. But would really like to know why this happened with this newer version of amplify cli.

priyaprabhakar07 · 2022-10-19T13:38:00Z

I have the same error message with parameter.json while trying to initialise amplify environment, once I downgrade to 10.2.3 it is fixed

I am keen to know why this happened in the latest amplify cli version(10.3.0) and
how to track whether this is fixed in the latest version?

josefaidt · 2022-10-19T14:28:07Z

Hey folks 👋 I was able to reproduce this issue using the following steps:

amplify init -y
amplify add auth
amplify update auth > add user pool groups
amplify push -y
git init
git clean -fXd remove gitignored from local directory (to simulate fresh clone)
amplify init --envName dev --yes

I've reopened this issue to track with 10.3.0

As a workaround, you can manually create a parameters.json file in the auth resource's build directory with an empty object as the contents {} prior to the headless init. In the case of Amplify Hosting, you can run this before amplifyPush --simple

cd amplify/backend/auth/<resource-name>/ && mkdir build && echo '{}' > build/parameters.json && cd -

josefaidt · 2022-10-19T14:54:59Z

Revisiting this, I'm going to re-close in favor of tracking the new active bug as a regression #11211

josefaidt added bug Something isn't working platform-init Issues related to initializing a new Amplify project labels Jan 12, 2022

josefaidt mentioned this issue Jan 18, 2022

Parameters.json location in new public project #9475

Closed

josefaidt mentioned this issue Feb 2, 2022

amplify pull failed to pull backend if it is imported #9674

Closed

4 tasks

josefaidt mentioned this issue Feb 16, 2022

unable to amplify pull project with auth, missing auth/.../build/parameters.json #9778

Closed

5 tasks

josefaidt added the auth Issues tied to the auth category of the CLI label Feb 21, 2022

InnovateWithEric added the p1 label Feb 21, 2022

InnovateWithEric assigned akshbhu Feb 23, 2022

akshbhu mentioned this issue Feb 24, 2022

fix: build resource when adding new env #9847

Merged

3 tasks

akshbhu mentioned this issue Mar 16, 2022

fix: build resource when adding new env #10003

Merged

3 tasks

akshbhu mentioned this issue Mar 22, 2022

fix: build resource when adding new env #10046

Closed

3 tasks

This was referenced Mar 22, 2022

chore(amplify_api): REST integration tests and change API provision script to use init aws-amplify/amplify-flutter#1188

Closed

Refactor to widgets and introducing the apiservice offlineprogrammer/amplify_expense_tracker#2

Merged

akshbhu mentioned this issue Mar 24, 2022

fix: build resource when adding new env #10058

Merged

3 tasks

josefaidt linked a pull request Apr 12, 2022 that will close this issue

fix: build resource when adding new env #10058

Merged

3 tasks

josefaidt closed this as completed Apr 12, 2022

josefaidt reopened this Oct 19, 2022

josefaidt added the regression Flair label to track regressions label Oct 19, 2022

josefaidt mentioned this issue Oct 19, 2022

Unable to build a project with amplify 10.3.0 #11211

Closed

5 tasks

josefaidt removed the regression Flair label to track regressions label Oct 19, 2022

josefaidt closed this as completed Oct 19, 2022

duranmla mentioned this issue Nov 8, 2022

DataStore does not sync join tables for guest users aws-amplify/amplify-js#10636

Closed

3 tasks

duranmla mentioned this issue Dec 6, 2022

Error trying amplify mock "Stream Arn must be specified" aws-amplify/amplify-category-api#858

Closed

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

unable to initialize project with auth from git, missing `auth/.../build/parameters.json` #9508

unable to initialize project with auth from git, missing `auth/.../build/parameters.json` #9508

josefaidt commented Jan 12, 2022 •

edited

stevenlafl commented Jan 23, 2022 •

edited

adi518 commented Feb 6, 2022 •

edited

Leandros commented Feb 9, 2022

swaminator commented Feb 14, 2022

adi518 commented Feb 14, 2022

phaedonmit commented Mar 17, 2022

danshev commented Mar 20, 2022 •

edited

may215 commented Apr 7, 2022

InnovateWithEric commented Apr 12, 2022

duranmla commented Oct 19, 2022

duranmla commented Oct 19, 2022

WebManifestation commented Oct 19, 2022

priyaprabhakar07 commented Oct 19, 2022

josefaidt commented Oct 19, 2022 •

edited

josefaidt commented Oct 19, 2022

unable to initialize project with auth from git, missing auth/.../build/parameters.json #9508

unable to initialize project with auth from git, missing auth/.../build/parameters.json #9508

Comments

josefaidt commented Jan 12, 2022 • edited

Before opening, please confirm:

How did you install the Amplify CLI?

If applicable, what version of Node.js are you using?

Amplify CLI Version

What operating system are you using?

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Amplify Categories

Amplify Commands

Describe the bug

Expected behavior

Reproduction steps

Workaround

GraphQL schema(s)

Log output

Additional information

stevenlafl commented Jan 23, 2022 • edited

adi518 commented Feb 6, 2022 • edited

Leandros commented Feb 9, 2022

swaminator commented Feb 14, 2022

adi518 commented Feb 14, 2022

phaedonmit commented Mar 17, 2022

danshev commented Mar 20, 2022 • edited

may215 commented Apr 7, 2022

InnovateWithEric commented Apr 12, 2022

duranmla commented Oct 19, 2022

duranmla commented Oct 19, 2022

WebManifestation commented Oct 19, 2022

priyaprabhakar07 commented Oct 19, 2022

josefaidt commented Oct 19, 2022 • edited

josefaidt commented Oct 19, 2022

unable to initialize project with auth from git, missing `auth/.../build/parameters.json` #9508

unable to initialize project with auth from git, missing `auth/.../build/parameters.json` #9508

josefaidt commented Jan 12, 2022 •

edited

stevenlafl commented Jan 23, 2022 •

edited

adi518 commented Feb 6, 2022 •

edited

danshev commented Mar 20, 2022 •

edited

josefaidt commented Oct 19, 2022 •

edited