![]() ![]() You can see how we handled it in connectapi::variant_render() here: rstudio/connectapi/blob/e88deb55b47414467d2720c4c625cbbea6194732/R/variant. There are some helpers to handle tasks (and I hope I did that right), but they are unfortunately pretty low level. It might be worth trying something like: library(connectapi) ![]() It's surprising you are getting an empty response though. Hey ! Interesting! Yeah, I am pretty sure that is a task ID. I'm wondering if this is just related to my version of RStudio Connect ( connect_version: 1.7.8-7), or if output logs are not provided when its triggered via the internal variants\render endpoint. Task_url <- paste0(rstudioconnecturl, "/_api_/v1/experimental/tasks/", task_id)Ĭontent(task_result)$output # this returns an empty list() Is this a task ID? I only ask because when I send it to the public task API endpoint, my output is empty: task_id <- content(send_render)$id The send_render will receive an httr object, and the content has an $id in it. Payload <- purrr::list_modify(payload, app_guid = content_id, variant_key = variant_key)Īdd_headers(Authorization = paste("Key", apikey))) I noticed that when I 'render': render_url <- paste0(rstudioconnecturl, '/_api_/variants/', variant_id, '/render?email=none
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |