Which python API? For what purposes? (ie, writing an ansible plugin?
module? some other tool?)
The python code that is used by the ansible application (for ex, the
'ansible.parsing.dataloader' python module) isn't
intended to be used by other applications. ie, there is no consideration
given to
I would consider it unusual, but it should work fine. Assuming there are no
expectations that the outer and inner ansible-playbook invocations are
sharing
internal data or state.
See
https://image.slidesharecdn.com/moretipsntricks-161011152406/95/more-tips-n-tricks-24-638.jpg?cb=1476199481
Need to provide the contents of touch.bash and the output from the ansible
commands using the '-vvv' verbosity level.
trying to run using yaml file .
>
paste the command line
I have written a custom module touch.bash to create a file
>
Note the builtin 'file' module does this, though I
/playbooks/oscheck.yml --tags kernel *
>
> Playbook get's executed successfully with providing the vault password
> file nor the prompt for a vault password and both the file's target.pass
> and target.yml are encrypted.
>
>
> From,
> Vino.B
>
>
>
>
> On Monday, March 19,
responses inline
On Mon, Mar 19, 2018 at 1:34 AM, Vino B wrote:
> Hi All,
>
>Request you help, after upgrade ansible to 2.6 -devel the password
> vault is not working as expected, and getting the below error, before the
> upgrade it was working fine without any
Making remote_tmp finer grained is on the roadmap for 2.5. That includes
per host remote_tmp.
https://github.com/ansible/ansible/issues/31022 is a tracking bug for
remote_tmp related bugs and features which
are intended to be fixed during 2.5 devel.
That looks like a bug in a module thats not in ansible/ansible but in
https://github.com/networktocode/ntc-ansible/blob/master/library/ntc_config_command.py#L244
(More specifically, like the error references, the 'output' var there isn't
defined there. Looks like either a indent/scope issue, or
t;changed\": true, \"queueslist\": [{\"q1\": {\"cache-size\": \"5000\",
> \"flowcontrol-start-queuesize\": \"-1\", \"propertyCount\": 5,
> \"cleanup-interval\": \"-1\", \"persistence-mode\": \"n
he, zf)
File "/home/ec2-user/ansible/lib/ansible/executor/module_common.py", line
466, in recursive_finder
tree = ast.parse(data)
File "/usr/lib64/python2.6/ast.py", line 37, in parse
return compile(expr, filename, mode, PyCF_ONLY_AST)
File "", line 163
Synt
First glance, looks like quoting issue. Module output seems to include a
mix of single and double quotes. module output should be json with double
quotes.
Looks like:
output = json.dumps(queuesList)
is going to make output a string with json in it. If you want the
structured data in the
For cases like this, the current approach is to move shared code into a
ansible.module_utils module and update cloudfront_facts and
cloudfront_distribution
to use the new module_utils.
Importing 'from ansible.modules.other_module' from my_module isnt
recommended, since 'other_module' wont be
Could you post a link to your changes that add a log function?
Usually items being logged multiple times means there are duplicate log
handlers attached to the loggers.
For the most part, a log handler will only need to be attached to the
'ansible' logger [1], if you are using the
standard
Thanks for the sample output. Working on test cases now.
On Tue, Jun 6, 2017 at 2:40 PM, Bruce V Chiarelli wrote:
>
>>> Any idea if that change will also be coming to FreeBSD/OpenBSD ?
>>
>> I remember it being discussed on the FreeBSD-current list ages ago, but
>> I don't
Could you get an example output from NetBSD 'ifconfig -a' before and after
the change?
If so, I'll add test cases and update the code.
Any idea if that change will also be coming to FreeBSD/OpenBSD ?
On Sunday, June 4, 2017 at 4:32:20 PM UTC-4, Bruce V. Chiarelli wrote:
>
> Upcoming
Ideally any facts needed by the module would be passed in task args.
How is the Facts(module) instance being used?
Previously, running Facts(module) in a module would result in
gathering all the facts again (if they had previously been collected
in setup...).
If you need to rerun some subset of
I'm guessing the system doesnt have 'repoquery' installed, and that is
potentially causing the plugin to lookup where rpm lives and for
whatever reason it is deciding rpm executable lives in /etc/rpm.
ie the result of
If you are working against the devel branch, then I suspect you have
stale lib/ansible/module/core and lib/ansible/module/extra dirs.
Failed to render doc for
../../lib/ansible/modules/core/utilities/logic/include_role.py
^ there is no /core/ path in devel any more
So likely trying to
I'll take it.
On Fri, Oct 7, 2016 at 1:05 PM, Hiroaki Nakamura wrote:
> Though I created the hostname module, I have never used it myself.
> I would like to resign as a hostname module maintainer
> since I would like to spend my spare time for other things.
>
> So could
Sounds like a good candidate for a ansible-modules-core issue at
https://github.com/ansible/ansible-modules-core/issues
(Would the yum_repository module be useful in this case?
http://docs.ansible.com/ansible/yum_repository_module.html)
On Fri, Oct 7, 2016 at 10:33 AM,
Working on a patch to improve this at the moment.
Attempting to replace the multiple (one per mtab entry) lsblk
invocations with a single 'lsblk' that collects info for all the blk
devices.
On Wed, Aug 10, 2016 at 2:32 AM, Paul Tötterman
wrote:
>> I would love to have
I have a wip branch at
https://github.com/alikins/ansible/tree/yamllint_on_yaml_error that
will also show yamllint output when yaml errors occur.
I found it useful when tracking down some bad yaml I was generating in unit
tests, but might not be generally useful. For the most part, to get to the
21 matches
Mail list logo