Deploys a bundle (tarball) to an Posit Connect server. If not provided,
name (a unique identifier) will be an auto-generated alphabetic string. If
deploying to an existing endpoint, you can set name or guid to the
desired content.
Usage
deploy(
connect,
bundle,
name = create_random_name(),
title = name,
guid = NULL,
...,
.pre_deploy = {
}
)
deploy_current(content)Arguments
- connect
A Connect object
- bundle
A Bundle object
- name
The unique name for the content on the server
- title
optional The title to be used for the content on the server
- guid
optional The GUID if the content already exists on the server
- ...
Additional arguments passed along to the content creation
- .pre_deploy
An expression to execute before deploying the new bundle. The variables
contentandbundle_idare supplied- content
A Content object
Details
This function accepts the same arguments as connectapi::content_update().
deploy_current() is a helper to easily redeploy the currently active bundle
for an existing content item.
See also
connectapi::content_update
Other deployment functions:
bundle_dir(),
bundle_path(),
bundle_static(),
download_bundle(),
poll_task()
Examples
if (FALSE) { # \dontrun{
client <- connect()
# beware bundling big directories, like `renv/`, `data/`, etc.
bnd <- bundle_dir(".")
deploy(client, bnd)
} # }
client <- connect(prefix = "TEST_1")
#> Error in connect(prefix = "TEST_1"): ERROR: Invalid (empty) API key. Please provide a valid API key
bnd <- bundle_path(system.file("tests/testthat/examples/static.tar.gz", package = "connectapi"))
#> Bundling path
deploy(client, bnd)
#> Error: object 'client' not found