Push

The push command facilitates the distribution of the packaged application to the ArconQ platform.

arq push [--alias <alias>] [-f, --file <path_to_arconq_file>] [--no-build]

Parameters:

• -a, --alias: (Optional) The alias or identifier of the application being pushed. If not specified, all applications defined in the .arconq file will be push.

• -f, --file: (Optional) Specifies the path to the .arconq configuration file. If not provided, the CLI looks for the file in the current folder.

• --no-build: (Optional) When provided, the build process is skipped before pushing the application(s). Useful for scenarios where you're certain the build is updated and you just want to push.

• -t, --tag: (Optional) Add tag to application revision. Tags are metadata (keyword or term) and can be used to categorize revisions. Multiple tags are allowed. If no alias is provided, than tag will be added to all applications from .arconq file. The argument takes precedence over those specified in the .arconq file. You can learn more about tags in this article.

• -p, --profile: (Optional) Specifies the profile which configuration will be used to connect with ArconQ instance. If no value is provided the default profile is used.

Examples:

1. Push a single application:

   arq push --alias basic-app

2. Push all applications from a file:

   arq push

3. Push without building:

   arq push --alias basic-app --no-build

4. Push a single application with tags:

   arq push --alias basic-app --tag sender --tag warehouse-A

5. Push all applications to an environment configured in the given profile:

   arq push -p prod