connectSPCSUser

<code>connectSPCSUser()</code> connects your Posit Connect account to the rsconnect
package so it can deploy and manage applications on your behalf.
Configure a
<a href="https://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-cli#location-of-the-toml-configuration-fil"><code>connections.toml</code> file</a>
in the appropriate location.
SPCS deployments require both Snowflake authentication (via the connection
name) and a Posit Connect API key. The Snowflake token provides proxied
authentication to reach the Connect server, while the API key identifies
the user to Connect itself.
If <code>snowflakeConnectionName</code> is not provided, rsconnect will attempt to
use the default Snowflake connection from the <code>connections.toml</code> file,
provided that the account matches the Connect server's URL.
Supported servers: Posit Connect servers

Programmatic deployment interface for 'RPubs',
'shinyapps.io', and 'Posit Connect'. Supported content types include R
Markdown documents, Shiny applications, Plumber APIs, plots, and
static web content.

Aron Atkins

rsconnect

Deploy Docs, Apps, and APIs to 'Posit Connect', 'shinyapps.io',
and 'RPubs'

Toph Allen

Hadley Wickham

Jonathan McPherson

JJ Allaire

Posit Software, PBC 

connectSPCSUser function

<dl><dt>account</dt>
<dd>A name for the account to connect.</dd>
<dt>server</dt>
<dd>The server to connect to.</dd>
<dt>apiKey</dt>
<dd>The API key used to authenticate the user</dd>
<dt>snowflakeConnectionName</dt>
<dd>Name of the Snowflake connection in
<code>connections.toml</code> to use for authentication or <code>NULL</code> to use the default
(when applicable).</dd>
<dt>quiet</dt>
<dd>Whether or not to show messages and prompts while connecting the
account.</dd></dl>

Arguments

<code>connectSPCSUser()</code> connects your Posit Connect account to the rsconnect
package so it can deploy and manage applications on your behalf.
Configure a
<a href='https://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-cli#location-of-the-toml-configuration-fil'><code>connections.toml</code> file</a>
in the appropriate location.
SPCS deployments require both Snowflake authentication (via the connection
name) and a Posit Connect API key. The Snowflake token provides proxied
authentication to reach the Connect server, while the API key identifies
the user to Connect itself.
If <code>snowflakeConnectionName</code> is not provided, rsconnect will attempt to
use the default Snowflake connection from the <code>connections.toml</code> file,
provided that the account matches the Connect server's URL.
Supported servers: Posit Connect servers

Register account on Posit Connect in Snowpark Container Services — connectSPCSUser

<dl>

<dt>account</dt>
<dd>A name for the account to connect.</dd>


<dt>server</dt>
<dd>The server to connect to.</dd>


<dt>apiKey</dt>
<dd>The API key used to authenticate the user</dd>


<dt>snowflakeConnectionName</dt>
<dd>Name of the Snowflake connection in
<code>connections.toml</code> to use for authentication or <code>NULL</code> to use the default
(when applicable).</dd>


<dt>quiet</dt>
<dd>Whether or not to show messages and prompts while connecting the
account.</dd>

</dl>

connectSPCSUser: Register account on Posit Connect in Snowpark Container Services

Description

Usage

Arguments