posit-dev / posit-dev/connectapi
New Article - Posit Connect Audit tasks?
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 54
- Forks
- 27
- Avg merge
- 1d 3m
- Merged PRs (30d)
- 1
Description
Looking at the articles on Posit support like https://support.posit.co/hc/en-us/articles/360007435274-Counting-Named-Users-in-Posit-Connect-and-Posit-Workbench-RStudio-Server-Pro, it would be useful to us to have connectapi equivalents.
For example:
library(tidyverse)
library(connectapi)
client <- connect(
host = Sys.getenv("CONNECT_PROD_SERVER"),
api_key = Sys.getenv("CONNECT_PROD_API")
)
audit <- connectapi::get_audit_logs(client, limit = 1000000)
most_recent_users <-
audit %>%
filter(user_id > 0) %>% # removes e.g. "Obsolete rendering remover" and "Auth Provider"
group_by(user_id, user_description) %>%
summarise(
MostRecent = max(time)
) %>%
arrange(desc(MostRecent)) %>%
filter(MostRecent > lubridate::today("UTC") - lubridate::years(1))
most_recent_users %>%
View()
Are the vignettes/pkgdown docs for this package a good place (the right place) for these? If so, we can look at helping with PRs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing vignettes and pkgdown documentation to determine whether this Posit Connect audit task belongs there. Use the provided connectapi example as the starting point, and consider the work complete when an agreed documentation location contains a usable equivalent of the referenced Posit support article.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100