开发者社区> 镜像站> NPM> @adobe/reactor-downloader
@adobe/reactor-downloader
Command line tool for downloading data from Adobe Launch to a local directory.
Last updated 9 months ago by bbythewa .
Apache-2.0 · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @adobe/reactor-downloader 
SYNC missed versions from official npm registry.

reactor-downloader

Command line tool for downloading a Launch property to a local directory.

Usage

Before running the downloader tool, you must first have Node.js installed on your computer. Your npm version (npm comes bundled with Node.js) will need to be at least 10.15.0. You can check the installed version by running the following command from a command line:

npm -v

You will also need to be authorized to use the Launch APIs. This is done by first creating an integration through Adobe I/O. Please see the Access Tokens Guide for detailed steps on creating an integration and procuring api access rights.

Finally, you must first have created a property in Adobe Launch to download.

Once you have a property ready to download and have an integraton created through Adobe I/O that can access the Adobe Launch APIs, you can use the bootstrapper tool in either a question-answer format or by passing information through command line arguments.

Question-Answer Format

To use the downloader in a question-answer format, run it by executing the following command from the command line:

npx @adobe/reactor-downloader

The tool will ask for any information necessary to download the repository.

Command Line Arguments

To skip any of the questions the downloader would typically ask, you can pass the respective information as command line arguments. An example is as follows:

npx @adobe/reactor-downloader --env=production --private-key=/Users/jane/launchkeys/reactor_integration_private.key --org-id=01C20D883A7D42080A494212@AdobeOrg --tech-account-id=14A533A72B181CF90A44410D@techacct.adobe.com --api-key=192ce541b1144160941a83vb74e0e74d --client-secret=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

The named parameters are as follows:

--env

The environment where the property exists. Valid options are development, qe, integration, and production. Users outside of Adobe will only use production.

--private-key (for authentication using an Adobe I/O integration)

The local path (relative or absolute) to the RSA private key. Instructions on how to generate this key can be found in the Getting Started guide and should have been used when creating your integration through the Adobe I/O console.

--org-id (for authentication using an Adobe I/O integration)

Your organization ID. You can find this on the overview screen for the integration you have created within the Adobe I/O console.

--tech-account-id (for authentication using an Adobe I/O integration)

Your technical account ID. You can find this on the overview screen for the integration you have created within the Adobe I/O console.

--api-key (for authentication using an Adobe I/O integration)

Your API key. You can find this on the overview screen for the integration you have created within the Adobe I/O console.

--client-secret (for authentication using an Adobe I/O integration)

Your client secret. You can find this on the overview screen for the integration you have created within the Adobe I/O console.

--access-token (for authentication using an access token)

A valid access token.

--save

A flag indicating whether to save the settings to a file for further use with other tools. This saves from having to type in the above going forward.

--settings-path

The location to save the settings. The file name should end in ".json". (defaults to ./reactor-settings.json)

Suggested Uses

This tool can be used in many ways, but here are a few suggested uses:

  • use in conjunction with reactor-sync.
  • If you are already storing the code that goes into Launch in repositories, this tool will be your best friend.
    • bootstrap your repository with a current Launch Property and all of it's code without having to download everything from Launch manually.
  • Run automated tests to ensure that your code doesn't have any obvious errors.
  • Run transpiles on your code automatically and then automatically sync it into Launch.
  • Run linters or code style enforcement tools to ensure that your code is always clean and you can always point to who is writing code in Launch that doesn't stay to standards.

If you have other use cases, let me know and I can update this list.

Contributing

Contributions are welcomed! Read the Contributing Guide for more information.

Licensing

This project is licensed under the Apache V2 License. See LICENSE for more information.

Current Tags

  • 0.2.1                                ...           latest (9 months ago)

3 Versions

  • 0.2.1                                ...           9 months ago
  • 0.2.0                                ...           9 months ago
  • 0.1.0                                ...           a year ago