[Feature Request] 1Password plugin enhancement

[jl9404]

Description

Right now, we can use op() function for 1-1 mapping with 1Password vault item. Would like to suggest that we could

• batch import env from 1Password text field
• download file from 1Password vault and store to target path

Motivation

No response

Proposed Solution

Batch import from 1Password text field

register a new root decorator importOp(id=instance_id, vault=op://vault-name/item-name/field-name)
parse and inject to the environment variable

Download file from 1Password vault and store to target path

register a new resolver function opFile(id=instance_id, vault=op://vault-name/item-name/field-name)
the environment variable value could be the target path, or maybe we can have extra arg for the path

e.g.

@opFile(id=instance_id, vault=op://vault-name/item-name/field-name)
MY_CERT=./secrets/my-cert.crt

or even it could be a root decorator if we simply just want to download the file from vault

Alternatives

No response

Additional Information

No response

[philmillman]

Thanks for this @jl9404, we have similar batch functionality in the DMNO equivalent plugin so it's on our roadmap for the varlock version as well.

The local file stuff is a great idea too. I know @theoephraim had some thoughts on caching that might influence that.

[theoephraim]

Thanks! These are great suggestions and things we've been thinking about for a while :)

I think we can accomplish them both in a slightly more generic way that will extend to other plugins in the future. Curious to hear what you think. Please chime in on the discussions.

---

For applying a set of values, I'm imagining a more general root decorator, something like @applyValues() which is meant to take in a set of values from somewhere and apply them all. You can then use the regular op function to fetch the value from 1pass, or imagine using another plugin to fetch it from somewhere else. You could have additional options for format (dotenv, json, yaml, etc). Perhaps other options I haven't thought of yet?

# @applyValues(op("op://..."))                            # default format is probably .env
# @applyValues(op("op://..."), format=json)     # but could set it to parse as JSON instead

I can however imagine a use case where you want to fetch a 1pass item (not a specific field) and apply all individual fields as env vars, using their labels as their keys. Or you could imagine something similar where you want to fetch a whole vault and apply all items. In this case, we would either need a new resolver function, or to add new options to op().

I've opened a discussion here -- #209

---

For file writing it's a little trickier - I've opened a discussion here - #210