Management

Private Preview | Advanced

Posit Team includes a Posit Package Manager management page for an administrator to perform post-installation operations.

Package Manager management menu

To manage Package Manager, click the menu icon (vertical dots) on the Package Manager card and click Manage.

Package Manager management page

Stop and start

The Package Manager service can be managed in several ways:

1. Manual stop and start.
2. Programmatic stop and start.

A suspended Package Manager service automatically resumes when visited by a user.

If there are times when Package Manager is not used, such as on weekends and holidays, suspending the service can help reduce your Snowflake compute costs.

Some features of Package Manager, such as scheduled syncs, do not run while the service is suspended.

You can manually stop and start the Package Manager service from the Manage page.

Package Manager service operations

You can start and stop the Package Manager service using SQL commands.

-- Start Package Manager
SELECT POSIT_TEAM.app.START_SERVICE('package-manager');

-- Stop Package Manager
SELECT POSIT_TEAM.app.STOP_SERVICE('package-manager');

Schedule the start and stop of Package Manager by running these SQL commands with Snowflake tasks.

-- Create a task to stop Package Manager at 6 PM daily.
CREATE OR REPLACE TASK task_packagemanager_stop
    SCHEDULE = 'USING CRON 0 18 * * * America/New_York'
AS
    SELECT POSIT_TEAM.app.STOP_SERVICE('package-manager');

-- Enable the stop task.
ALTER TASK task_packagemanager_stop RESUME;

-- Create a task to start Package Manager at 8 AM daily
CREATE OR REPLACE TASK task_packagemanager_start
    SCHEDULE = 'USING CRON 0 8 * * * America/New_York'
AS
    SELECT POSIT_TEAM.app.START_SERVICE('package-manager');

-- Enable the start task.
ALTER TASK task_packagemanager_start RESUME;

Upgrade

Note

Posit frequently upgrades the Posit Team Native App and its associated version of Package Manager. When the Posit Team Native App is updated, Posit Team automatically upgrades Package Manager.

Some configuration changes require a service upgrade before they take effect. For example, you need a service upgrade after modifying the target compute pool or uploading a new license. The management page indicates when configuration changes require an upgrade. Click the Upgrade button to upgrade Package Manager.

Package Manager upgrade

Change configuration

In the management page you can change the license or compute pool sizing. Click Save Changes once you have made changes and refresh the page. If the compute pool or license has changed, an upgrade is required. Follow the upgrade section instructions.

Resize compute pool

The Manage page lets you change the compute pool used to run Package Manager. Choose a compute pool size appropriate to your workload requirements.

Package Manager compute pool

Use the upgrade instructions to apply a compute pool change and restart Package Manager.

Backup and restore

Posit Team supports easily creating Package Manager backups. Simply specify a backup name or leave it blank for a randomly assigned name and click Save New Backup.

Create backup

Next, wait several minutes for the backup to be created.

Backup created

Restoring from a backup takes about 10 minutes. You can delete backups that are no longer needed.

Logs

You can view logs of the Package Manager installation.

Package Manager logs

User access

In order for Snowflake users to access Package Manager, you must grant access to their user roles. We recommend you grant the application role POSIT_TEAM_USER to most users.

Snowsight UI

GRANT APPLICATION ROLE POSIT_TEAM.POSIT_TEAM_USER TO ROLE YOUR_USER_ROLE;

To restrict user access to Package Manager only, give the application role POSIT_PACKAGE_MANAGER_USER to those users. See Managing Application Roles to learn more.

Snowsight UI

GRANT APPLICATION ROLE POSIT_TEAM.POSIT_PACKAGE_MANAGER_USER TO ROLE YOUR_USER_ROLE;

Package Manager groups

You can create additional application roles to use as groups in Posit Package Manager. Administrators can use “groups” to associate or control access to repositories for users to view, publish, or download packages.

To add a new application role, click on User Roles and Access in the Management page for Package Manager.

Management link

Add your custom application role to the Managing roles table and press Create.

User access

Package Manager administration

You can currently only administer Package Manager through Workbench due to Snowflake SPCS authentication requirements.

Within Workbench, log in to Package Manager using the pre-installed rspm command. Note that Package Manager admin credentials are only available to users with the POSIT_PACKAGE_MANAGER_ADMIN or POSIT_TEAM_ADMIN application role.

rspm login sso --address=https://package-manager

Click on the SSO link and copy the device code.

Once logged in, visit the Package Manager Admin CLI docs to learn how to configure repositories, sources, Git builders, package security, and much more.

Change the egress

Package Manager requires external access to two endpoints to function. Additional endpoints like github.com may be required for Git Builder functionality. See the following table for endpoints.

Endpoints	Required	Description
rspm-sync.rstudio.com:443	Yes	Required for syncing packages to the internal Package Manager
github.com:443	No	Required for Git builders that need to pull packages from GitHub

Editing the default egress policy requires the ACCOUNTADMIN role. You can modify the default egress policy for Package Manager by:

• Using the Snowsight UI (recommended) or
• Writing your own SQL

To edit network rules via the Snowsight UI:

Visit Governance & security -> Network policies -> Network Rules.

Network rule edit

Edit the given network rule named POSIT_TEAM_APP_DATA.DATA.PACKAGE_MANAGER_PUBLIC_EGRESS and remember to include the required endpoints detailed in the security egress documentation.

To edit network rules via SQL:

Modify the existing network rule POSIT_TEAM_APP_DATA.DATA.PACKAGE_MANAGER_PUBLIC_EGRESS.

Snowsight UI

DESCRIBE NETWORK RULE posit_team_app_data.data.package_manager_public_egress;

-- include custom <host>:<port>
-- host names are allowed
-- this example policy allows all ips on port 80 and 443
ALTER NETWORK RULE posit_team_app_data.data.allow_all_rule SET VALUE_LIST('0.0.0.0:80', '0.0.0.0:443');

Modify the egress rules only after a successful installation, and only change one rule at a time, allowing two to three minutes for each rule to take effect.

Troubleshooting and support

Visit the troubleshooting page for known issues and troubleshooting steps. If none of the troubleshooting steps help, please contact support or click on the Support button in the navigation header.

Support link