Fix inverted TLS variables in zabbix_proxy role#5
Open
paulo-ruiz wants to merge 2 commits intoLibreDevOps:libredevops-master-devfrom
Open
Fix inverted TLS variables in zabbix_proxy role#5paulo-ruiz wants to merge 2 commits intoLibreDevOps:libredevops-master-devfrom
paulo-ruiz wants to merge 2 commits intoLibreDevOps:libredevops-master-devfrom
Conversation
added 2 commits
January 26, 2026 19:55
The task configuring the zabbix_proxy API object incorrectly mapped `tls_connect` and `tls_accept`, using the opposite variables. This resulted in wrong TLS configuration being applied to the proxy. Corrected the mapping so that: - tls_connect uses zabbix_proxy_tlsconnect - tls_accept uses zabbix_proxy_tlsaccept
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The task configuring the zabbix_proxy API object incorrectly mapped
tls_connectandtls_accept, using the opposite variables. This resulted in wrong TLS configuration being applied to the proxy.Corrected the mapping so that:
This PR is is awaiting approval in upstream