- req
vector of characters that represents the call (e.g. c("projects", project_id, "events")
)
- api_root
URL where the GitLab API to request resides (e.g. https://gitlab.myserver.com/api/v3/
)
- verb
http verb to use for request in form of one of the httr
functions
httr::GET()
, httr::PUT()
, httr::POST()
, httr::DELETE()
- auto_format
whether to format the returned object automatically to a flat data.frame
- debug
if TRUE API URL and query will be printed, defaults to FALSE
- gitlab_con
function to use for issuing API requests (e.g. as returned by
gitlab_connection()
- page
number of page of API response to get; if "all" (default), all pages
(up to max_page parameter!) are queried successively and combined.
- max_page
maximum number of pages to retrieve. Defaults to 10. This is an upper limit
to prevent gitlabr getting stuck in retrieving an unexpectedly high number of entries (e.g. of a
project list). It can be set to NA/Inf to retrieve all available pages without limit, but this
is recommended only under controlled circumstances.
- enforce_api_root
if multiple pages are requested, the API root URL is ensured
to be the same as in the original call for all calls using the "next page" URL returned
by GitLab This makes sense for security and in cases where GitLab is behind a reverse proxy
and ignorant about its URL from external.
- argname_verb
name of the argument of the verb that fields and information are passed on to
- ...
named parameters to pass on to GitLab API (technically: modifies query parameters of request URL),
may include private_token and all other parameters as documented for the GitLab API