On Fri, Apr 1, 2022 at 10:27 PM Richard Hector wrote:
>
> Hi all,
>
> Currently my inventory is stored in the same git repo as my play(book)s,
> roles etc, which I don't like.
Consider using git submodules if you want a unified workspace.
> What are common ways to avoid this? Perhaps keep
Hi all,
Currently my inventory is stored in the same git repo as my play(book)s,
roles etc, which I don't like.
What are common ways to avoid this? Perhaps keep inventory in a subdir
which is .gitignored, and make that a separate repo?
I also want to keep data which is not strictly
"Container ship" is pretty clear. Others include:
"Tupperware".
"Mixing bowls"
"Measuringcups"
"Russian Dolls"
"Turtles All The Way Down".
"The inevitable product of people taught only recursion as a valid way
to do anything"
"Pay no attention to that server behind the layer of abstraction"
Hi all,
I have several leased VPS in which I run LXC containers.
At the moment, the group I use for those is "lxc_hosts", but that has a
few problems:
- Everything in inventory is a host, so lxc_host could just as well be a
container as the machine it lives on.
- Separators in general are
Ouch! Then you'd have to put the tasks into their own tasks file, and
use |include_tasks| ...
Or give |backuppc_client_mysql_dump| a reasonable ||default(...)| so
that the looped task(s) would do no harm.
blocks are not a way to skip tasks, a 'when' on a block is just fortasks inside
the
blocks are not a way to skip tasks, a 'when' on a block is just for
tasks inside the block to inherit.
> So one solution would be to put both tasks in a block, and put the `when:
> backuppc_client_mysql_dump is defined` condition on the block itself.
--
--
Brian Coca
--
You received
json:
"ec2_asg": {
"changed": false,
"failed": false,
"results": [
{
"tags": [
{
"key": "peer_discovery_backend",
"propagate_at_launch": true,
