Posit Connect storage backend with graceful fallback — user_pins

Resolves the storage backend for the session_mgmt_backend blockr.core::blockr_option() – of which it is the default – in three tiers, degrading instead of erroring on a missing credential:

Usage

user_pins_board(session = get_session())

Arguments

session: Shiny session whose request carries the Connect user session token; defaults to the current reactive domain.

Value

A pins_board: a viewer- or application-scoped board_connect, or board_local when no Connect credentials are available.

Details

When the visitor carries a Posit Connect user session token (the Connect API Integration is enabled), it is exchanged via connectapi::connect() for a viewer-scoped API key, so each user reads and writes pins under their own namespace (pins::board_connect()). Requires the connectapi package.
With no visitor token but application Connect credentials in the environment (CONNECT_SERVER and CONNECT_API_KEY), a board on the application's own account.
Otherwise (e.g. local development, off Connect), pins::board_local().

Set the session_connect_tag blockr.core::blockr_option() to an existing Connect tag's name (or a "Category/Name" path) to have the workflow listing filter server-side by that native tag; saves then apply it. A top-level tag is a category: naming one lists everything tagged beneath it, but saves cannot apply it, as Connect assigns only nested tags. Unset, the listing returns every pin and checks blockr membership only on load.

Examples

if (FALSE) { # \dontrun{
  # Resolves the backend for the current visitor; call from within a
  # running Shiny app, as it reads the session request for a Connect
  # user session token. It is the default value of the
  # `session_mgmt_backend` blockr option.
  board <- user_pins_board()
} # }