It needs a specific subdir for each plugin type, otherwise there would
be name conflicts across plugins.
See
https://docs.ansible.com/ansible/latest/dev_guide/developing_locally.html#local-plugins
--
--
Brian Coca
--
You received this message because you are subscribed to the
not a development question. Use ansible-project ML or go to #ansible
on freenode.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, sen
Something like this will sort the keys and use the last one.
- debug: msg={{ansible_lvm.vgs[(ansible_lvm.vgs.keys()|sorted|list)[-1]]}}
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe
Yes, here are the docs:
https://docs.ansible.com/ansible/latest/user_guide/vault.html#multiple-vault-passwords
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop
Just to confirm, what Andreas describes is correct, any 'shared' code
must be in module_utils, modules cannot rely on other module's code as
ONLY the current module code (+ module_utils references) is shipped to
the remote.
--
--
Brian Coca
--
You received this message
Up to 2.9 there is no independent version of modules included in
Ansible, after 2.10 and moving into collections you can see the
'collection version' .. but no module version yet.
--
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
a loop of 100 items.
>
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
Depends, this can happen at many points and for diff reasons, in
general `|string` filter when you consume it ensures it is a string,
if it is happening at YAML boundry quote it or use !!str
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
https://hitchdev.com/strictyaml/why/implicit-typing-removed/ <= its
the opposite of yours, but same issue
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and s
sible for the play's gather_facts
(normally still calls setup module)
- gather_facts supports configurable set of modules (network_os
resolution already built in)
- gather_facts can run multiple modules in parallel
--
--
Brian Coca
--
You received this message because you are
h ignore, it is very dependant on the method/code used to
do the gathering, which can vary by platform, OS, distro, distro
version, etc. I have not found a good way to handle that yet.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible
e can also affect the controller by occupying the forks for
too long and delaying the play in general.
--
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving ema
Just added this for 2.12 (still not final)
https://github.com/ansible/ansible/pull/73707
Also see https://github.com/ansible/ansible/pull/74331
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To u
no actual limit in code, you might be limited by resources or other
external factors.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from i
tasks do not use return codes, their status is reflected in the return
data dictionary as keys.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emai
You also have --limit , which avoids playbook rewrites and per run
custom inventories
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from i
I was not aware of the datetime bug (was thinking to_datetime &
strftime), but it is still simple to do in jinja:
- debug: msg='{{seconds}}'
vars:
d: "{{res['delta'].split(':')}}"
seconds : "{{ d[0]|int * 3600 + d[1]|int * 60
ways there, inject just adds the
ansible_mounts alias)
To find out what exactly is happening i recommend running fact
gathering directly on the targets that you see are missing
ansible_mounts (unless it is the 'inject' issue, which is controller
configuration).
--
--
Brian Co
;mount + error message specific to each mount.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-deve
ansible-core 2.11 and 2.12 have many of the improvements
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ans
ned documentation, it is in git after all) and I'm
confident that our record would speak against any perceived bias, as
long as you are willing to examine all the facts.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible
ping['msg']
for the specific auth errors you can rescule
rescue:
- action: do stuff here
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving
The cliconf/network_cli plugins do this, they handle the connection
internally in the module and use ssh/paramiko/libssh to interact with
the target
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development"
twork.html
main dev guide
https://docs.ansible.com/ansible/latest/dev_guide/index.html
more communication channels (see network working group, they are most
likely to have better answers about this type of development )
https://docs.ansible.com/ansible/latest/community/communication.html
------
you have `module_rejectlist`, but it requires `module_blacklist`
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
To view this discussion on the web vi
Many ways, just an example:
- in a handler update a host_vars/.yml with the list of users
already synced, notify when sync tasks run/change
- add to sync role/block/tasks a conditional based on the variable
cdreated `when: username not in already_processed_users`
--
--
Brian Coca
Actually I was already thinking of spliting _modify_module, for one, it
should not need/handle/know about become_kwargs and we should eliminate the
passing of these, which is kind of the opposite direction of your
proposal.
As for action plugins, they already do too much and have too much
in
Jinja2 has this already, macros
https://jinja.palletsprojects.com/en/2.10.x/templates/#macros
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emai
most other use cases.
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
To vie
ins themselves at the remote
via a temporary agent, but then this also limits us to python in many
respects and removes several abilities (changing
become/connection/interpreter settings per loop item, for example).
--
Brian Coca
--
You received this message because you are subscribed to
s:
testlist_initial_value: [10,11]
merge_pattern: '^.+_merge_list'
a_merge_list: [1,2,3]
b_merge_list: [4,5,6]
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscr
, but each
task/host has it's own fork.
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@
It is possible, just not via the variable, do `import sys;
sys.version_info < (3, 0)`, since that will reflect the python the
script is running under.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
T
Modules should not have direct access to vault secrets, but you can
provide them to module options via the unvault/vault filters: (last
ones in section)
https://docs.ansible.com/ansible/latest/user_guide/playbooks_filters.html#hashing-and-encrypting-strings-and-passwords
--
--
Brian Coca
other side effects that you can track, but hard
to build them all into the command/shell modules (open port/service
running/package installed/etc) but there are plenty of other actions
that can query this.
--
--
Brian Coca
--
You received this message because you are subscribed to the G
Also, if the built in command does not do exactly what you want, you
are free to create your own custom version, it just not make sense for
this in the core offering.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Develo
--syntax-check playbook.yml `, for vars
files i would use `ansbile -m include_vars `, for roles `ansbile -m
import_role ...`
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this grou
collection.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
To view this dis
with something unusable, hence the limitation to only
depend on code in module_utils/.
https://docs.ansible.com/ansible/latest/reference_appendices/module_utils.html
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development&qu
sorry, wrong link before
https://docs.ansible.com/ansible/latest/dev_guide/developing_module_utilities.html
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop
symlinks do work, but you still need an ansible_collections/ dir
before your collection
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails fro
ls -l ~/.ansible/collections/ansible_collections/
total 20
lrwxrwxrwx 1 bcoca bcoca 54 Oct 7 2021 bcoca ->
/home/bcoca/work/collections/ansible_collections/bcoca
On Wed, Feb 22, 2023 at 3:45 PM Brian Coca wrote:
>
> symlinks do work, but you still need an ansible_collections/ dir
it is not really effective until the 'next play' as modifying the
current play's data is very problematic.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this
es that had been fed into it.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.c
against the terminal plugin).
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
evant advice.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
To view thi
' for more information.
Looks like typo in a shell command/script (meant `cat`?) or `ucat` is
not in the PATH
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group an
riables you need.
If this was possible in 2.9, which it was not, it would have been a
major bug and security issue.
The 'working' example you show seems to get a full dictionary of the
parameters passed to the module via the 'endpoint' option, I don't see
any other w
and cloud libraries.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
with core in favor of your own.
--
------
Brian Coca (he/him/yo)
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@
which will
automatically be transformed to JSON. This will effectively be the same as
'the better modules' I mention above and will be 'transparent' to users,
eventually eliminating the problem and confusion.
--
Brian Coca
--
You received this message because you are su
*sigh* that is new one ... the module is doing a check it shouldn't, we
need to fix that in the module itself.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and
There is one in the queue already:
https://github.com/ansible/ansible-modules-extras/pull/2208
I personally would separate container from image management.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development"
Either is fine, currently this is only for display, so whatever conveys the
message.
We might change this in the future as we automate validation of
requirements.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development"
the skippy is the one which ONLY hides skipped tasks, actionable also hides
OK tasks.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, sen
task headers get printed before a task gets attempted for any of the hosts,
the callback hides the skipped hosts but cannot 'unprint' the headers if
all hosts skip the task.
The only way to do that would be to buffer the output and wait until all
hosts skip.
------
Brian Coc
the RC1 for 2.1.1 should be out soon.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@google
return the info or not.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For mo
you probably want hostnameoutput.stdout
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-deve
They are complementary, the Options tuple is simulating 'command line
options', which still get overridden by connection variables.
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubsc
For sudo(by default) the user would be the 'login/remote' user which can
change by play/task/host. For su it would be the user you 'become', which
can also vary as at every level. So there is really no good way to present
this info at the 'global' prompt for password
http://github.com/ansible/proposals
once we have proposals, we can consider adding it to a roadmap.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emai
ns, visit https://groups.google.com/d/optout.
>
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups
hostvars always has all hosts present in inventory, you can also look at
groups['all'] to get the full list.
--
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this grou
The module_utils directory is the proper place for it and a do_common.py
can be added there.
After 2.2 is released we plan on merging all repos into a single one to
avoid the 2 PRs issue with this feature.
--
Brian Coca
--
You received this message because you are subscribed to the
changed_when/failed_when are there to deal with modifying a task output
status, callbacks execute AFTER this happens, so even if you modify the
data it won't modify the actual status of the tasks.
--
Brian Coca
--
You received this message because you are subscribed to the G
es will make things clearer and help us get through the
backlog faster. As always we welcome your feedback.
--
Brian Coca
Ansible Core Team
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group
er plays,
'include_tasks' can ONLY occur inside a play (roles are already inside a
play).
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiv
vars_files is a PLAY directive, not part of includes
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-deve
ally needs
some work).
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For
For Ansible Tower support please email supp...@ansible.com or open a ticket
at https://support.ansible.com.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiv
The ansible-galaxy command line already supports installing from them, so
no changes needed there.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emai
@Ricardo, on the galaxy.ansible.com (galaxy-server) side, it only allows
importing roles from github.com as well as requires github.com accounts.
I believe they want to extend the server software to allow for other
'origins' both for accounts and for shared roles.
------
Brian Coc
Since Ansible is not a server and does not offer APIs in a way you can
access with curl, I"m going to assume you want to use Tower, which is not
what we support in this mailling list.
please go to https://support.ansible.com.
--
Brian Coca
--
You received this message because yo
The best way is normally to just look at open issues, see if there is
something that looks small and in your bailiwick and try to tackle it.
There is also an #ansible-devel channel in IRC if you want quick response
to questions.
--
Brian Coca
--
You received this message because you
This is not currently a feature, but you can open an Issue and someone
might implement it.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from i
To debug, run with -vvv and you'll see the full ssh command, see if you can
run that manually.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving
when: runs INSIDE the with_items loops, so it cannot prevent definition
errors, use |default([]) as an empty list will skip the loop.
http://docs.ansible.com/ansible/playbooks_conditionals.html#loops-and-conditionals
--
Brian Coca
--
You received this message because you are
implemented yet.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For
Just to make sure everyone is on the same page and our process is clear to
all, I've added a PR for 'committer docs' to the community repo.
https://github.com/ansible/community/pull/134
--
Brian Coca
--
You received this message because you are subscribed to th
add an assert in each role that checks if the variables you
need for that role are defined or not at the start, as it is self contained
you can predict your external needs at that point, anything else will be
expensive to run and fragile.
--
Brian Coca
--
You received this message because
Nothing exists yet, but I have this proposal
https://github.com/ansible/proposals/issues/24 that would do 'just that'
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from
You have already have a "jail" connection plugin, which most modules should
be able to use transparently.
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and s
ed, so you get 3 OK,
one of them also changed
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@g
make your first action
- meta: end_play
when:
http://docs.ansible.com/ansible/meta_module.html
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving e
Please don't comment on closed issues as we don't see those normally.
------
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send
It means that adding new options is OK, removing or changing the behaviour
of existing ones should be avoided. New options don't break backwards
compatibility AKA break existing plays.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
&qu
Most older versions should be vulnerable, we recommend upgrading to 2.1 or
2.2 once we release the fix.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving e
The environment: directive exists so each module does not need to implement
what you are asking.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emai
It is for setting environment variables, it should not execute anything.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
once ready we will push to all the normal channels we control (including
pypi), until then you can try out the RC at
http://releases.ansible.com/ansible/ansible-2.2.1.0-0.4.rc4.tar.gz
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"An
a discussion about this, I encourage feedback,
not only on this post but on the proposals linked above.
There are many a topic in the mailing lists and on Github issues that are
also pertinent to this discussion, I omitted them as I believe the
proposals already take most of those into account.
-
Correction on my previous email: i mean @svg .. not @sivel, though he has
contributed to these discussions my tab completion gave me the wrong nick
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development"
specific
marker would be the recommended approach.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-deve
We've been adding rules and normalizing module development to try to
keep a consistent interface, the problem is the existing modules
cannot easily be rewritten w/o breaking playbooks.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
&qu
You want --sytnax-check, but that will only give you an approximation
as dynamic includes and include_role can change the number of tasks,
as can tags and conditionals.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Develo
lity to 'fail' using that
module or 'assert', a workaround is using a block with conditionals to
apply to the 'rest of the tasks' in the play.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Deve
You can use any libs included with python core, for example we use
distutils's version, in many modules you can see examples of using
LooseVersion and StrictVersion
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Developm
It is part of 2.3 release, coming soon.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-deve
1 - 100 of 185 matches
Mail list logo
