[Experimental] Deploy a git repository directly to RStudio Connect, using RStudio Connect's "pull-based" "git-polling" method of deployment.

deploy_repo(
  client,
  repository,
  branch,
  subdirectory,
  name = create_random_name(),
  title = name,
  ...
)

deploy_repo_enable(content, enabled = TRUE)

deploy_repo_update(content)

Arguments

client

A Connect R6 object

repository

The git repository to deploy

branch

The git branch to deploy

subdirectory

The subdirectory to deploy (must contain a manifest.json)

name

The "name" / unique identifier for the content. Defaults to a random character string

title

The "title" of the content

...

Additional options for defining / specifying content attributes

content

An R6 Content object (i.e. the result of content_item())

enabled

Whether Connect will enable automatic polling for repository updates

Value

A ContentTask object, for use with poll_task() (if you want to follow the logs)

Details

  • deploy_repo_enable() enables (or disables) RStudio Connect's git polling for a piece of content

  • deploy_repo_update() triggers an update of the content from its git repository, if any are present

See also

connectapi::poll_task, connectapi::repo_check_branches, connectapi::repo_check_manifest_dirs

Other content functions: acl_add_user(), content_delete(), content_item(), content_title(), content_update(), create_random_name(), dashboard_url_chr(), dashboard_url(), delete_vanity_url(), get_acl_user(), get_bundles(), get_environment(), get_image(), get_jobs(), get_vanity_url(), git, permissions, set_image_path(), set_run_as(), set_vanity_url(), swap_vanity_url(), verify_content_name()