Ketare proxy na mai kula don uwar garken Ansible WinRM ɗaya
Da Ansible-core 2.19 da pywinrm 0.5.0, aika YAML null ta hanyar WinRM extras tare da barin tabbatar da takardar shaidar a kunne.
Don wata hanyar WinRM ta ciki da ke wucewa bisa kuskure ta proxy na intanet na mai kula, saka waɗannan ƙima a cikin masu canjin uwar garke ko rukuni da suka dace tare da saitunan haɗin da ake da su:
ansible_winrm_proxy: null
ansible_winrm_server_cert_validation: validateWannan siffa ta shafi Ansible-core 2.19 tare da pywinrm 0.5.0. Ƙarin yana aika ansible_winrm_* da ake goyon baya zuwa pywinrm; YAML null yana zama Python None.
pywinrm 0.5.0 yana bayyana proxy=None a matsayin kashe hanyar wucewa ta proxy kuma yana ba da alamar no_proxy ta zama tare da kiyaye sauran tsarin muhalli da TLS na yau da kullum. transport.py da aka shigar baya buƙatar gyara.
Don amfani da pywinrm kai tsaye, aika proxy=None zuwa Protocol. A wannan sigar, takamaiman adireshin proxy yana zaɓar wannan matsakaici, yayin da barin zaɓin yana riƙe tsohuwar ɗabi'ar da ta dogara da muhalli.
Daidaita siffar lissafin da API na ƙarin: ƙarni da ke ba da zaɓin proxy mai nau'i zai iya rubuta alamar zance maimakon wannan hanyar extras/null. Mai kula har yanzu yana buƙatar hanyar sadarwa zuwa uwar garken Windows, kuma gazawar amincewar HTTPS tana buƙatar daidaitaccen tsarin CA. server_cert_validation: validate ya kamata ya ci gaba da aiki.