Skip to content

Conversation

@eb4x
Copy link
Collaborator

@eb4x eb4x commented Sep 1, 2025

SUMMARY

Swap out uri for win_uri and some minor cleanups related to the change.
zabbix_agent_version_long check suggested by @patrik-plastik in #1589
Fixes #1621
Fixes #1627

ISSUE TYPE
  • Feature Pull Request
COMPONENT NAME

roles/zabbix_agent

ADDITIONAL INFORMATION

Requires ansible.windows: ">=2.8.0"

eb4x added 4 commits September 1, 2025 10:31
win_uri was introduced in ansible.windows collection v2.8.0
Only set zabbix_agent_version_long if not already defined. Allows
for running the version of your own choosing, incase a downgrade
is needed. Updating some documentation to reflect the change.

Check suggested by @patrik-plastik.
@eb4x eb4x changed the title Win uri roles/agent/windows: uri => win_uri Sep 1, 2025
@eb4x eb4x requested a review from pyrodie18 September 1, 2025 09:34
Copy link
Collaborator

@pyrodie18 pyrodie18 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went ahead and approved but want to just toss some food for thought before you merge.

  1. Is this a breaking change? I could argue yes because we're pinning a version of Windows which we never have before. If I remember correctly, it came out in March so it is entirely possible users haven't downloaded it. But its also with the Windows part of the collection which we've always said was simply best effort.
  2. I'll be honest. I still don't totally understand what the issue creator is trying to do and why this run on the windows host vs the controller like it is supposed to which leads me to the question of does this fall within the 80% rule or does this fall into a edge case where they are better off forking and making what appears to be a very simple change.

FYI those comments are related to the one task and not the variable cleanup which I have zero issues with.

@eb4x
Copy link
Collaborator Author

eb4x commented Sep 2, 2025

  1. Is this a breaking change? I could argue yes because we're pinning a version of Windows which we never have before. If I remember correctly, it came out in March so it is entirely possible users haven't downloaded it. But its also with the Windows part of the collection which we've always said was simply best effort.

Agreed.

  1. I'll be honest. I still don't totally understand what the issue creator is trying to do and why this run on the windows host vs the controller like it is supposed to which leads me to the question of does this fall within the 80% rule or does this fall into a edge case where they are better off forking and making what appears to be a very simple change.

Yeah, I don't quite know how this gets executed on the Windows host unless he commented out the delegate_to. But it was kind of a hack anyway, and I think win_uri is the cleaner way to go.

FYI those comments are related to the one task and not the variable cleanup which I have zero issues with.

The variable name cleanup is probably more of a breaking change, as users might have put values under the previous names, but it's been broken a while so 🤷

@eb4x eb4x merged commit e15cd36 into ansible-collections:main Sep 2, 2025
123 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants