Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spcs support #651

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

spcs support #651

wants to merge 3 commits into from

Conversation

edavidaja
Copy link
Collaborator

initial support for interacting with Connect in SPCS

Intent

Type of Change

  • Bug Fix
  • New Feature
  • Breaking Change

Approach

Take an optional dependency on the snow CLI
commands requiring interaction with remote servers gain an optional --snowflake-connection-name argument
The ingress URL, account name, and keypair configured out of band are sufficient information
to obtain the OAuth token required to interact with Connect in SPCS.

supports rsconnect add, details, and deploy_html

Automated Tests

Directions for Reviewers

Checklist

  • I have updated CHANGELOG.md to cover notable changes.
  • I have updated all related GitHub issues to reflect their current state.

@@ -234,9 +234,33 @@ def __init__(
self.ca_data = ca_data
# This is specifically not None.
self.cookie_jar = CookieJar()
# 🤡
self.snowflake_connection_name = None

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious as to why this is needed here but not in the other non SPCS targetable servers.

pass a --snowflake-connection-name argument to the CLI, which uses
the snow cli to obtain connection details and perform token exchange
on each call to connect

supports rsconnect add, details, and deploy_html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants