Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update is not very "ansible like" when same data results in "changed: true" #68

Open
gav- opened this issue Oct 7, 2022 · 0 comments
Open

Comments

@gav-
Copy link

gav- commented Oct 7, 2022

Summary

Updating an existing item with onepassword.connect.generic_item module, with the same exact properties and values, results in "changed: true". This is not very ansible-like, it should really be "changed: false"

Use cases

No changes should result in no changes.

Proposed solution

No changes should result in no changes.

Is there a workaround to accomplish this today?

Use onepassword.connect.item_info to read the data first, compare with data to be submitted, and skip onepassword.connect.generic_item task if they are the same. This is non-trivial in ansible (1password items can be quite complex) and would be better handled in the module.

References & Prior Work

Compare to ansible.builtin.user module where the same properties result in no change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant