Add Databricks support for service principals when running in Posit Connect with connectcreds#931
Conversation
4103d9f to
288ec4c
Compare
|
I backed out the formatting-only changes from this and squashed + rebased the commits. I also set the |
|
Thank you!! Do yall want to see this change going in the odbc release to be submitted early next week? If so, on what timeline would you imagine connectcreds would be submitted to CRAN? |
|
@simonpcouch We haven't been able to get it to work yet, so I'd say no, don't hold up the release. |
288ec4c to
a6ea354
Compare
| #' server <- function(input, output, session) { | ||
| #' conn <- DBI::dbConnect( | ||
| #' odbc::databricks(), | ||
| #' workspace = "https://example.cloud.databricks.com", |
There was a problem hiding this comment.
Would it make sense to add this same example parameter to the first dbConnect example here? Or it uniquely applicable inside the Shiny server?
There was a problem hiding this comment.
We detect the workspace parameter automatically in most cases, so this is really just a way to show how you'd override it if necessary.
This commit adds support for service principal credentials managed by Posit Connect alongside our existing support of viewer-based credentials. The meat of this is handled by the `connectcreds` package. Documentation and unit test updates are included. Co-authored-by: Aaroon Jacobs <aaron.jacobs@posit.co> Signed-off-by: Aaron Jacobs <aaron.jacobs@posit.co>
0049661 to
2696845
Compare
CANNOT MERGE untilconnectcredsreleaseThis commit adds support for service principal credentials managed by
Posit Connect alongside our existing support of viewer-based
credentials. The meat of this is handled by the
connectcredspackage.Documentation and unit test updates are included.
Addresses: #930