The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Create, inspect, update, and delete Google Cloud Secret Manager secrets and their versions directly from R. The package wraps the Secret Manager API v1 and uses 'gargle' for authentication, supporting interactive OAuth, service account keys, and pre-existing tokens. Secret and version metadata are returned as S3 objects with print methods that avoid revealing secret values, and listing operations return data frames with one row per secret or version. Default project settings, labels, filters, and the full version lifecycle (add, access, enable, disable, and delete) are supported.
| Version: | 0.2.1 |
| Depends: | R (≥ 4.1) |
| Imports: | cli, dplyr, gargle (≥ 1.5.2), glue, httr (≥ 1.4.0), jsonlite (≥ 1.8.0), lifecycle, purrr, rlang, utils |
| Published: | 2026-11-12 |
| DOI: | 10.32614/CRAN.package.googlesecretmanager (may not be active yet) |
| Author: | Brancen Gregory [aut, cre] |
| Maintainer: | Brancen Gregory <brancengregory at gmail.com> |
| License: | MIT + file LICENSE |
| URL: | https://brancengregory.github.io/googlesecretmanager/ |
| NeedsCompilation: | no |
| Materials: | README, NEWS |
| CRAN checks: | googlesecretmanager results |
| Reference manual: | googlesecretmanager.html , googlesecretmanager.pdf |
| Package source: | googlesecretmanager_0.2.1.tar.gz |
| Windows binaries: | r-devel: not available, r-release: not available, r-oldrel: not available |
| macOS binaries: | r-release (arm64): not available, r-oldrel (arm64): googlesecretmanager_0.2.1.tgz, r-release (x86_64): not available, r-oldrel (x86_64): not available |
Please use the canonical form https://CRAN.R-project.org/package=googlesecretmanager to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.