Closed gsingh91 closed 1 year ago
updated code to use vetiver_deploy_rsconnect
@SamEdwardes can you please review?
Hey at Gagan - the content has been failing since the update. Were you able to re-run the document on Workbench? For your reference, here are the logs from Connect.
Also, not that we are using vetiver_deploy_rsconnect
do we need to create the client
object?
app_name <- "bike-predict-r-api"
app_title <- "Bike Predict - Model - API"
# Establish a connection to RStudio connect.
client <- connectapi::connect(
server = Sys.getenv("CONNECT_SERVER"),
api_key = Sys.getenv("CONNECT_API_KEY")
)
# Deploy the content.
vetiver_deploy_rsconnect(
board = board,
name = pin_name,
version = NULL,
appTitle = app_title,
)
@SamEdwardes I am able to reproduce locally. I was able to test it before as I was using my Connect credentials and my own pin. Have reverted my changes to continue the previous deployments. working on making this change locally for now.
raised an issue on vetiver for Connect deployment: https://github.com/rstudio/vetiver-r/issues/151
Thanks Gagan!
The issue seems to be with my Colorado env, so I tested the changes locally. Created PR #37 , @SamEdwardes can you please do a quick test and merge? Thanks
Current version uses
rsconnect
to deploy the vetiver API. we should update it to usevetiver_deploy_rsconnect
function instead.