apprun-cli is a command line interface for AppRun β Sakura Cloud.

This is an unofficial tool.

See also https://manual.sakura.ad.jp/cloud/manual-sakura-apprun.html

Usage: apprun-cli <command> [flags] Flags: -h, --help Show context-sensitive help. --debug Enable debug mode ($DEBUG) --app=STRING Name of the application definition file ($APPRUN_CLI_APP) --tfstate=STRING URL to terraform.tfstate ($APPRUN_CLI_TFSTATE) -v, --version Show version and exit. Commands: init --name=STRING [flags] Initialize files from the existing application deploy [flags] Deploy an application list [flags] List applications diff [flags] Show diff of applications render [flags] Render application status [flags] Show status of applications delete [flags] Delete the application versions [flags] Manage versions of application traffics [flags] Manage traffics of application user <operation> [flags] Manage apprun user url [flags] Show application public URL Run "apprun-cli <command> --help" for more information on a command. 

$ go install github.com/fujiwara/apprun-cli/cmd/apprun-cli@latest 

or brew install fujiwara/tap/apprun-cli

or download from Releases

Action fujiwara/apprun-cli installs apprun-cli binary into /usr/local/bin. This action installs the specified version of apprun-cli.

If args is specified, it runs apprun-cli <args> after installation. (Added in v0.4.0)

jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - uses: fujiwara/apprun-cli@v0 with: version: v0.3.3 # version-file: .apprun-cli-version - run: |  apprun-cli deploy --app app.jsonnet

jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - uses: fujiwara/apprun-cli@v0.4.0 with: version: v0.4.0 args: deploy env: APPRUN_CLI_APP: app.jsonnet SAKURACLOUD_ACCESS_TOKEN: ${{ secrets.SAKURACLOUD_ACCESS_TOKEN }} SAKURACLOUD_ACCESS_TOKEN_SECRET: ${{ secrets.SAKURACLOUD_ACCESS_TOKEN_SECRET }}

Note:

• version is not required, but it is recommended that the version be specified.
• version-file can also specify the version by using the file containing the version without the v prefix (for example, 0.3.0).
• args is optional. If it is specified, it runs apprun-cli <args> after installation.

apprun-cli reads configuration from environment variables.

• SAKURACLOUD_ACCESS_TOKEN
• SAKURACLOUD_ACCESS_TOKEN_SECRET

AppRun is a global resource, so you don't need to specify the zone or region.

apprun-cli list lists all applications.

$ apprun-cli list {  "created_at": "2024-12-31T14:07:36.90833+09:00",  "id": "ff7abff9-eacc-44ef-b92d-ab0f65fe8ed4",  "name": "example",  "public_url": "https://app-ff7abff9-eacc-44ef-b92d-ab0f65fe8ed4.ingress.apprun.sakura.ne.jp",  "status": "Success" } {  "created_at": "2024-12-31T14:27:39.918056+09:00",  "id": "e8e32d63-2260-4093-aef2-c277b375de4e",  "name": "example2",  "public_url": "https://app-e8e32d63-2260-4093-aef2-c277b375de4e.ingress.apprun.sakura.ne.jp",  "status": "Success" }

apprun-cli init --name=example shows the application definition to stdout.

You can save the output to a file and edit it to deploy the application.

Note: The password is not set in the output.

Usage: apprun-cli init --name=STRING [flags] Initialize files from existing application Flags: --name=STRING name of the application to init --jsonnet Use jsonnet to generate files 

$ apprun-cli init --name example 2024/12/31 14:18:05 INFO initializing app=example 2024/12/31 14:18:05 INFO found id=04946938-e424-463d-b6ad-9ce5e03de55d {  "components": [  {  "deploy_source": {  "container_registry": {  "image": "example.sakuracr.jp/example:latest",  "password": null,  "server": "example.sakuracr.jp",  "username": "apprun"  }  },  "env": [  {  "key": "FOO",  "value": "baz"  }  ],  "max_cpu": "1",  "max_memory": "2Gi",  "name": "example",  "probe": {  "http_get": {  "path": "/",  "port": 8080  }  }  }  ],  "max_scale": 2,  "min_scale": 0,  "name": "example",  "port": 8080,  "timeout_seconds": 60,  "packet_filter": {  "is_enabled": true,  "settings": [  {  "from_ip": "192.0.2.0",  "from_ip_prefix_length": 24  }  ]  } }

You can manage the application with the following commands.

The following commands require the application definition file specified by --app flag or APPRUN_CLI_APP environment variable.

apprun-cli deploy deploys the application.

We recommend to use Jsonnet format to read environment variables. See also Jsonnet

When the application is not found, apprun-cli deploy creates a new application.

local must_env = std.native('must_env'); local tfs = std.native('tfstate'); { components: [ { deploy_source: { container_registry: { image: tfstate('sakuracloud_container_registry.example.fqdn') + '/debian:latest', password: must_env('REGISTRY_PASSWORD'), server: tfstate('sakuracloud_container_registry.example.fqdn'), username: 'apprun', }, }, env: [ { key: 'FOO', value: 'bar', }, ], max_cpu: '1', max_memory: '2Gi', name: 'example', probe: { http_get: { path: '/', port: 8080, }, }, }, ], max_scale: 2, min_scale: 0, name: 'example', port: 8080, timeout_seconds: 60, packet_filter: { is_enabled: true, settings: [ { from_ip: '192.0.2.0', from_ip_prefix_length: 24, }, ], }, }

apprun-cli diff shows the difference between the current application and the definition file.

--- 0b523faa-b0de-4c26-bc42-a3ff500b9367 +++ app.jsonnet @@ -12,7 +12,7 @@ "env": [ { "key": "FOO", - "value": "bar" + "value": "baz" } ], "max_cpu": "1",

apprun-cli render shows the rendered application.

--jsonnet flag enables Jsonnet format for rendering.

apprun-cli status shows the status of the application.

{  "created_at": "2024-12-31T14:27:39.918056+09:00",  "id": "e8e32d63-2260-4093-aef2-c277b375de4e",  "name": "example2",  "public_url": "https://app-e8e32d63-2260-4093-aef2-c277b375de4e.ingress.apprun.sakura.ne.jp",  "status": "Success" }

apprun-cli url shows the public URL of the application.

$ apprun-cli url https://app-example-eacc-44ef-b92d-ab0f65fe8ed4.ingress.apprun.sakura.ne.jp

This URL is also shown in the public_url field of the list and status commands.

This is useful to get the URL in scripts. For example:

$ curl $(apprun-cli url)

apprun-cli delete deletes the application.

apprun-cli versions manages the versions of the application.

Flags: --id=STRING Show the detailed information of the specified version id --delete Delete the specified version id --force Force delete without confirmation 

If no flags are specified, it shows the list of versions.

--id shows the detailed information of the specified version id.

--delete deletes the specified version id. Requires --id flag.

--force forces delete without confirmation. default is false.

apprun-cli traffics manages the traffics of the application.

Flags: --set=KEY=VALUE,... Set traffic percentage for each version --shift-to=STRING Shift all traffic to the specified version --rate=100 Shift rate percentage(per minute) --period=1m Shift period --[no-]rollback-on-failure Rollback to the previous version if failed to shift 

If no flags are specified, it shows the current list of traffics.

--set sets the traffic percentage for each version.

The value is a comma-separated list of version_name=percentage. The version name is shown in the list of versions command.

For example, the following command sets the traffic to 50% for each version.

$ apprun-cli traffics \  --set app-0b523faa-b0de-4c26-bc42-a3ff500b9367=50,app-ff7abff9-eacc-44ef-b92d-ab0f65fe8ed4=50

The sum of the traffic percentage must be 100.

--shift-to shifts all traffic to the specified version from the current version.

--rate specifies the shift rate percentage per minute. The default is 100 (immediate).

--period specifies the shift period. The default is 1m.

--rollback-on-failure rolls back to the previous version if failed to shift. The default is true. If you want to disable it, specify --no-rollback-on-failure.

For example, the following command shifts all traffic to the specified version with a 10% rate per 30 seconds.

$ apprun-cli traffics \  --shift-to app-0b523faa-b0de-4c26-bc42-a3ff500b9367 \  --rate 10 \  --period 30s

apprun-cli user manages the user for AppRun.

Before using apprun-cli, you need to create a user only at once.

• apprun-cli user create creates a new user.
• apprun-cli user read confirms the user is created.

apprun-cli supports Jsonnet to read the application definition.

You can use Jsonnet to read environment variables from the environment using functions via std.native.

local must_env = std.native('must_env'); local env = std.native('env'); { foo: must_env('FOO'), bar: env('BAR', 'default'), }

• must_env reads the environment variable and returns the value. If the environment variable is not set, it raises an error.
• env reads the environment variable and returns the value. If the environment variable is not set, it returns the default value.

You can use Jsonnet to read the resource value in terraform.tfstate from the URL using functions via std.native.

local tfstate = std.native('tfstate'); { server: tfstate('sakuracloud_container_registry.foo.fqdn'), }

• tfstate lookups the value from terraform.tfstate and returns the value.

--tfstate flag or APPRUN_CLI_TFSTATE environment variable is required to specify the URL to terraform.tfstate.

$ apprun-cli deploy --app app.jsonnet --tfstate https://example.com/terraform.tfstate

Supported URL schemes are http, https, file, s3(Amazon S3), gs(Google Cloud Storage), remote(Terraform Cloud) and azurerm(Azure Blob Storage).

For more information, see tfstate-lookup.

You can use Jsonnet to read secret values from Sakura Cloud Secret Manager using functions via std.native.

local secret_value = std.native('secret_value'); { components: [ { deploy_source: { container_registry: { password: secret_value('your-vault-id', 'registry-password', null), }, }, }, ], }

• secret_value(vault_id, secret_name, version) reads the secret value from Secret Manager.
  • vault_id: Resource ID of the Secret Manager Vault (string)
  • secret_name: Name of the secret (string)
  • version: Version number of the secret (number or null for the latest version)

The Secret Manager API uses the same authentication credentials as AppRun API (SAKURACLOUD_ACCESS_TOKEN and SAKURACLOUD_ACCESS_TOKEN_SECRET).

For more information about Secret Manager, see Sakura Cloud Secret Manager Documentation.

MIT

Fujiwara Shunichiro (@fujiwara)