az_webapp: Manage web apps

Description Usage Arguments Functions

View source: R/webapp.R

Description

Manage web apps

Usage

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

Arguments

slot

The name of the deployment slot. Defaults to the production slot if not specified. Only available for higher app service plan tiers.

restart

whether to restart the web app.

...

Arguments passed on to az_cli_run

cmd

Command, required, optional, additional, extra parameters, as for processx::run() add parameters are reserved for the user to pass down additional arguments to the Azure CLI. extra parameters are reserved for internal use.

req

Command, required, optional, additional, extra parameters, as for processx::run() add parameters are reserved for the user to pass down additional arguments to the Azure CLI. extra parameters are reserved for internal use.

opt

Command, required, optional, additional, extra parameters, as for processx::run() add parameters are reserved for the user to pass down additional arguments to the Azure CLI. extra parameters are reserved for internal use.

add

Command, required, optional, additional, extra parameters, as for processx::run() add parameters are reserved for the user to pass down additional arguments to the Azure CLI. extra parameters are reserved for internal use.

echo_cmd

Whether to print the command to run to the screen.

echo

Whether to print the standard output and error to the screen. Note that the order of the standard output and error lines are not necessarily correct, as standard output is typically buffered.

name

Name of the web app. (In the Azure CLI, this argument is sometimes known as name, and sometimes as web).

plan

Name or resource id of the app service plan.

resource_group

The Azure resource group to which the app service should belong.

deployment_container_image_name

The custom image name and optionally the tag name. Image must

  • include everything needed to run the shiny app, including shiny itself, but does not need to include shiny server or other software to route, load balance and serve shiny,

  • include an ENTRYPOINT and/or CMD instruction to start shiny automatically (recommended), or shiny must be started via the startup_file argument.

startup_file

docker run [COMMAND] to use inside of your custom image deployment_container_image_name. Defaults to NULL, in which case the container is expected to start up shiny automatically (recommended). For details on the shiny startup command, see the examples.

The [EXPR] (anything after -e) must not be quoted, and must not contain spaces (#27). For example, the following startup-files are valid (if nonsensical, because they don't start a shiny app)

  • "Rscript -e 1+1" (no spaces)

  • "Rscript -e print('foo')" (no spaces, no quoting of the [EXPR])

The following startup-files are invalid:

  • "Rscript -e 1 + 1" (spaces inside [EXPR])

  • "Rscript -e '1+1'" (quoting of [EXPR] would be treated as "Rscript -e '\"1+1\"'").

subscription

Name or ID of the Azure subscription to which costs are billed. According to an upvoted answer on Stack Overflow, Azure subscription IDs need not be considered a secret or personal identifiable information (PII). However, depending your applicable context and policies, you may want to provide this argument as a secret.

To find out which subscriptions you are currently authorised to use, run print(az_account_list()).

docker_registry_server_url

The container registry server url. Defaults to NULL, in which case the azure default, docker hub is used.

docker_registry_server_user, docker_registry_server_password

Credentials for private container registries. Defaults to NULL for public registries. Do not expose your credentials in public code; it's best to use secret environment variables.

Functions


subugoe/AzureAppService documentation built on Nov. 24, 2020, 5:39 a.m.