David Gunter

Thanks for submitting this PR! I'm in favor of merging this in. That said, would it make sense to have this as a configurable toggle (with a default to `True`)?

Thanks for contributing! This looks good to me and we'll get to merging it soon.

@hgarrow If you're using the Raft protocol, it sounds like this _may_ be an issue with the Vault configuration. Hashicorp has a section in their plugin documentation about the error...

Thanks for that information! Really appreciate your help getting to the bottom of this. I noticed in the logs you posted earlier (https://github.com/1Password/vault-plugin-secrets-onepassword/issues/9#issuecomment-865004726 ) that Vault returned a 403: Permission...

Hey @gaborpeter - thanks for reporting this. We definitely should highlight the difference between `urls` at the root level and adding a url as a `field`. I'll make sure this...

Could you open that as a separate issue? Then we'll definitely see what we can do :)

👋 Thanks for reporting this issue! It's definitely not the behavior we intended. This is caused by how Ansible interprets `no_log` and how we create those generated values. As you...

I agree this would be useful! Unfortunately the Ansible module needs information about the item before determining what to do next. For example, if you didn't provide an `item_id` and...

> in the case where item_id is provided, it would be safe to just interpret `state: present` as requesting a blind update, `state: absent` would be requesting a blind delete....

Confirming the `ansible-test sanity` tests pass sounds like a good first step for this while we continue researching better integration test automations. We'll want to split this issue into two:...