You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using brocade_facts module and setting https: True doesn't work correctly in release 2.0.0. Connection is still done via http. Setting https: self is doing https connection.
to https=dict(required=True, type='bool') makes it work again. I doubt this parameter was ever tested correctly. What's so hard in using real certificates?
The text was updated successfully, but these errors were encountered:
I have merged this change into the external develop branch. You can take this fix and let us know if this resolves the issue that you are seeing:
diff --git a/utils/brocade_url.py b/utils/brocade_url.py
index 8e00e6a..49f6050 100644
--- a/utils/brocade_url.py
+++ b/utils/brocade_url.py
@@ -25,6 +25,7 @@ VF_ID = "?vf-id="
HTTP = "http://"
HTTPS = "https://"
SELF_SIGNED = "self"
+HTTPS_ENABLED = "true"
From the beginning, we considered fos_https a string with three values: True, False, and Self. But somehow, it got exposed with the credentials marked https as the string type.
We will incorporate the changes in the next patch release.
Using brocade_facts module and setting
https: True
doesn't work correctly in release 2.0.0. Connection is still done via http. Settinghttps: self
is doing https connection.Result was:
Ansible Environment
Redefining the argument_spec in brocade_facts
ansible/library/brocade_facts.py
Line 244 in d4dcce8
to
https=dict(required=True, type='bool')
makes it work again. I doubt this parameter was ever tested correctly. What's so hard in using real certificates?The text was updated successfully, but these errors were encountered: