Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.amplify.aws/gen1/javascript/tools/console/adminui/extend-cli/ below:

Website Navigation

• Skip to main content

Extend with the Amplify CLI - JavaScript

Amplify Studio allows you to use all the Amplify CLI's features without the need to configure it with AWS Identity and Access Management (IAM). Changes made in Amplify Studio can be made available in the CLI by running the amplify pull command. Similarly, CLI changes to the data model or auth will be visible in Amplify Studio. For all other categories, Studio provides links to the relevant service consoles in AWS.

1. Open a terminal window and install the CLI.

After the Amplify CLI finishes installing, you can configure the CLI so that you can use it without an AWS account.

Open Amplify Studio. Choose Local setup instructions in the header and copy the amplify pull command.

Open a terminal window and navigate to the directory where you would like to have Amplify setup your project. To initialize Amplify in the current directory, run the following command. Replace the xxx values with your unique appId and envName.

A browser window opens and prompts you to continue logging in to the Amplify CLI. Choose Yes.

Return to the terminal window. You should see the following success statement:

The Amplify CLI is now configured and you can use it to provision new cloud backend features.

The Studio Set up menu lists cloud backend features such as functions, storage, and APIs that you can add to your app using the CLI. For each backend resource, Studio displays the CLI commands to run in your terminal window.

1. In Studio, on the Set up menu, choose Storage or Functions.
2. On the Storage page, under Pull your Amplify project, copy the following command and run it in your terminal window.
3. After your backend environment has been successfully pulled from the cloud, copy the following command under Add storage capabilities and paste it in your terminal window:

1. Follow the prompts in the terminal window to configure storage with your desired settings.
2. Run the following command in your terminal window to build your local backend resources and provision them in the cloud:

1. Return to the Studio Storage page. Confirm that a link to your new storage resource is available in the Deployed storage resources section.

All backends created in Amplify Studio and Amplify CLI are deployed using AWS CloudFormation. AWS CloudFormation allows you store your backend configuration as code in your repository. This has three major benefits:

1. Ability to extend a project with capabilities offered by individual services (e.g. Cognito, DynamoDB) that are not available in Amplify.
2. Ability to easily replicate backend environments across AWS accounts and regions.
3. Ability to easily integrate with CI/CD pipelines such as the pipeline offered in the Amplify console.

All backend infrastructure-as-code definitions can be added to your project with the Amplify Command Line Interface (CLI).

Amplify Studio does not support building certain Amplify CLI added resources such as:

1. Lambda functions
2. Resource overrides

This behavior is observed when running a Amplify CLI amplify pull --appId <appID> --envName <envName> command in the terminal, which opens a new tab in the browser with a Amplify Studio login screen. On logging in, if you are not redirected back and observe the CLI being stuck in a loading state.

To resolve this issue,

1. Exit from the Amplify CLI prompt
2. If present, remove the leftover artifacts created in your current directory (e.g. amplify or amplify-backup) from the failed pull attempt
3. Rerun the Amplify CLI amplify pull --appId <appID> --envName <envName> command

When using Amplify CLI, you may encounter the following error message:

Failed to receive expected authentication tokens. Error: [Error: 'jsonString' argument missing or empty]

This message occurs when running a Amplify CLI amplify pull --appId <appID> --envName <envName> command in the terminal and allowing access permission to the CLI.

To resolve this issue,

1. Delete the config.json file present at the location ~/.amplify/admin/
2. If present, remove the leftover artifacts created in your current directory (e.g. amplify or amplify-backup) from the failed pull attempt
3. Rerun the Amplify CLI amplify pull --appId <appID> --envName <envName> command

Note, the content of ~/.amplify/admin/config.json is utilized to store JWTs to vend temporary AWS credentials and should **NOT be shared.

A flag to disable overrides has been detected, please deploy from a different environment. at buildOverrideDir

A flag to disable custom resources has been detected, please deploy from a different environment. at buildResource

The errors mentioned above occur during deployment if your Amplify project contains an override.ts file or custom resources are deployed. Amplify Studio does not support deploying projects with override files or custom resources.

To resolve this error, remove the override.ts file and any custom resources from your project, then run amplify push. Alternatively, you can use Amplify CLI to build and push your resources; however, deploying with Amplify Studio will not be possible.

Resources such a UI Library, Data manager, User management and File browser will not be effected by this behavior.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4