An interface to the RequestTracker API.
To start using the
rt package, log in to your RT instance by setting the server URL in using
Sys.setenv and use
rt_login() to log in and store your session locally.
Below, we log into Best Practical's demo installation of RT:
library(rt) Sys.setenv("RT_BASE_URL" = "https://demo.bestpractical.com") rt_login() # Enter demo/demo
Once you are successfully logged in, you're all set to use the package.
rt package supports all of the RequestTracker REST API:
Note: Most of these functions support being chained together (for example, with the
See the included vignettes for more information about usage.
To log out, use the
rt_logout function (or restart your R session):
A test suite is provided that is comprised mostly of integration tests that are configured to run against a local installation of RT.
By default, running
devtools::test() will only run a small subset of the full test suite: those that do not depend on being able to call out to an RT installation (i.e., unit tests).
To run the full test suite locally,
Start a local RT installation with Docker:
docker run -d --name rt -p 80:80 netsandbox/request-tracker
Turn on integration tests for your session
Sys.setenv("RT_INTEGRATION" = TRUE)
devtools::test() from the same session as (2)
All API calls go through an intermediate state as an
rt_api object, which is made up of three parts:
content, generally returned as a tibble/data frame
pathor URL that was accessed
responsefrom the API.
This is mainly to help normalize out some of the inconsistencies in the RT API itself and make implementing the API call wrappers easier.
Let us know about any issues or bugs.
Support was provided by the National Center for Ecological Analysis and Synthesis, a Center funded by the University of California, Santa Barbara, and the State of California.
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.