Closed acidroper closed 2 years ago
Hello, @acidroper
Thanks for the very detailed report. I've confirmed this as a problem and I'll look into it.
Thanks,
Rhys
Hello @acidroper,
Fix included in https://github.com/ansible-collections/community.cassandra/pull/206
You can see the test cases I've used here https://github.com/ansible-collections/community.cassandra/pull/206/files#diff-f2f13f26302f5d98877b657a6e3c4eda0c3d2e71b229f99f548427fdf55a984a
Rhys
Fix merged.
Hello @rhysmeister,
Thanks for the fix. Could you tell me please, when the new version with the fix will be available on Ansible Galaxy?
Hello @acidroper,
Not sure when I'll get the time exactly but probably not too long. You can get the latest build from here https://github.com/ansible-collections/community.cassandra/releases/tag/latest
Cheers,
Rhys
Release to Galaxy done: https://galaxy.ansible.com/community/cassandra
SUMMARY
When the
keyspace_permissions
parameter is set to"ALL PERMISSIONS"
for a certain keyspace (not for the 'all_keyspaces' key), the result of cassandra_role execution is always "changed". First, it grants the permissions, then it revokes them, then it grants them again, and so on.ISSUE TYPE
COMPONENT NAME
cassandra_role
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Host: Manjaro Linux Target: Debian 11
STEPS TO REPRODUCE
Run the task multiple times.
EXPECTED RESULTS
"changed": false
ACTUAL RESULTS
The first run:
The second run:
One more run: