vault backend

[richfitz]

I'm working on a package that wraps vault - https://github.com/vimc/vaultr

So two related thoughts:

• does it make sense to add vault as an alternative backend to your package? It's very useful when the aim is to share secrets across machines and is cross platform (this was suggested on the ropensci slack)
• do you have a timeline for release of your package to CRAN - I would be interested in using the system keychain in securing access to the access tokens to vault but you do have a big scary warning about changes so am wondering how far along things are for a stable API

[gaborcsardi]

@richfitz

It does make sense to have a vault backend. I am not sure which package it would go to. Maybe a third package?

I can put keyring on cran, no changes are needed to it.

Sent from my Samsung SM-G361F using FastHub

[richfitz]

Looking at the structure of the package, I was thinking I could add it directly to vaultr. But a third package might make sense too (less sense if I use keychain to fetch things like github tokens to authenticate with vault)

[richfitz]

(and reading my initial comment please read "add vault as an alternative backend to your package" as add vault as an alternative backend for your package").

Is there documentation for writing backends, especially on testing that they conform to expected behaviour?

[gaborcsardi]

MAkes sense. You can decide if you want it in another package or not.

As for backend docs, probably not (sorry, on my phone now), but it should be pretty straightforward, just look at an existing backend. I can add docs if you are unsure about sg.

[richfitz]

Cool, sounds good. I have no crazy timeline on this but will keep you posted

[gaborcsardi]

I will close this now for lack of activity. Please reopen as needed.