Hello there,
I'm using the win_dns_record module in tower 3.8.3 in Openshift, but it
doesn't seem to have an option to put the credentials to be used, or at
least not documented.
The only way to fill in the required "ansible_user" and "ansible_password"
credentials is explicitly in the "extra
Ok, after finding the last version of my ansible container that worked and
digging around in the galaxy collection versions. I managed to fix it by
installing the collection community.windows at version 1.5.0,
This should keep me going for now :) Although I'm interested to know if I
can help
I should add that we've been using this in various playbooks for a while
now. It mysteriously stopped working some time between the 9th of August
and the 21st of September. Although, that is quite dependant on when our
ansible build process ran and picked up new dependency versions.
Cheers
Howdy,
I am also seeing this issue.
chris:~/git/ansible$ ansible -m community.windows.win_dns_record -a
"type=CNAME computer_name='dc1.example.local' name=myapp
zone='internal.example.co.uk' ttl=60 value='docker1.example.local'" -i
inventory/test.yml admgmthost -vvv
ansible [core 2.11.5]
Welp, time to integrate that myself.
Thanks for the assist Matt.
On Tuesday, September 14, 2021 at 11:40:01 AM UTC-4 Matt Martz wrote:
> That issue appears to have been fixed in the collection, but the
> change has not been included in a release yet:
>
>
That issue appears to have been fixed in the collection, but the change has
not been included in a release yet:
https://github.com/ansible-collections/community.windows/pull/277
On Tue, Sep 14, 2021 at 10:24 AM jesse...@gmail.com
wrote:
> Alrighty
>
> So I'm behind the curve and am updating
Alrighty
So I'm behind the curve and am updating all of my collections and testing
out playbooks here and there, and I noticed along the way that from between
community.windows 1.1.0 to 1.6.0 that there has been a major change to how
this module is handling computer_name:
Namely, right before
OK,
Am I missing something? or is this module requiring you to run it against
the DNS server directly?
I know I though powershell normally can define the DNS server I wish to
execute against, but this module doesn't look like I can tweak that any,
without adding the feature manually.
How
