Updates the requirements on
[ansible-core](https://github.com/ansible/ansible) to permit the latest
version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/ansible/ansible/releases">ansible-core's
releases</a>.</em></p>
<blockquote>
<h2>v2.18.2</h2>
<h1>Changelog</h1>
<p>See the <a
href="https://github.com/ansible/ansible/blob/v2.18.2/changelogs/CHANGELOG-v2.18.rst">full
changelog</a> for the changes included in this release.</p>
<h1>Release Artifacts</h1>
<ul>
<li>Built Distribution: <a
href="a7dc8c6042/ansible_core-2.18.2-py3-none-any.whl">ansible_core-2.18.2-py3-none-any.whl</a>
- 2216676 bytes
<ul>
<li>c337512d740d9d9606846e1b1620eaaeadccb6dc2e864ce92cb485a8fc1f57f4
(SHA256)</li>
</ul>
</li>
<li>Source Distribution: <a
href="ccf2e5ac2f/ansible_core-2.18.2.tar.gz">ansible_core-2.18.2.tar.gz</a>
- 3076683 bytes
<ul>
<li>725b047d35942304eb322eb934b98cc5442ac3f49d33827d97171c238c4b69b9
(SHA256)</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="7c5e00274b"><code>7c5e002</code></a>
New release v2.18.2 (<a
href="https://redirect.github.com/ansible/ansible/issues/84615">#84615</a>)</li>
<li><a
href="b4dfc6a660"><code>b4dfc6a</code></a>
Update Ansible release version to v2.18.2rc1.post0. (<a
href="https://redirect.github.com/ansible/ansible/issues/84586">#84586</a>)</li>
<li><a
href="95bf4dd427"><code>95bf4dd</code></a>
New release v2.18.2rc1 (<a
href="https://redirect.github.com/ansible/ansible/issues/84583">#84583</a>)</li>
<li><a
href="ee0084dbcf"><code>ee0084d</code></a>
Ansible.Basic - Fix required_if check (<a
href="https://redirect.github.com/ansible/ansible/issues/84562">#84562</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84582">#84582</a>)</li>
<li><a
href="5f5e5d321b"><code>5f5e5d3</code></a>
ssh - Improve CLIXML stderr parsing (<a
href="https://redirect.github.com/ansible/ansible/issues/84569">#84569</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84580">#84580</a>)</li>
<li><a
href="0d44d0fde4"><code>0d44d0f</code></a>
ansible-test - fix coverage for test modules (<a
href="https://redirect.github.com/ansible/ansible/issues/84366">#84366</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84401">#84401</a>)</li>
<li><a
href="420287e83d"><code>420287e</code></a>
fix incongruent ansible-vault cli options (<a
href="https://redirect.github.com/ansible/ansible/issues/84494">#84494</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84552">#84552</a>)</li>
<li><a
href="3e22739cc8"><code>3e22739</code></a>
fix warnings about reserved variable names to cover all sources (<a
href="https://redirect.github.com/ansible/ansible/issues/84432">#84432</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84">#84</a>...</li>
<li><a
href="2ab0976f0e"><code>2ab0976</code></a>
gather_facts, fix 'smart' handling with network os and 'setup' (<a
href="https://redirect.github.com/ansible/ansible/issues/84425">#84425</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84471">#84471</a>)</li>
<li><a
href="2870532035"><code>2870532</code></a>
Make sure we are always using Lock from our multiprocessing context (<a
href="https://redirect.github.com/ansible/ansible/issues/84453">#84453</a>)
...</li>
<li>Additional commits viewable in <a
href="https://github.com/ansible/ansible/compare/v2.16.0...v2.18.2">compare
view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Empty blocks are no longer added to the graph.
- Tasks in role should not have the `[task]` as a prefix.
- `Node.index` can be `None`. This mean they will not be added to the
graph (for graphviz and mermaid).
- Fix `CompositeNode.is_empty()`
Ansible executor engine treats them very differently:
- All `import*` statements are pre-processed at the time playbooks are
parsed.
- All `include*` statements are processed as they are encountered during
the execution of the playbook.
From
https://docs.ansible.com/ansible/2.9/user_guide/playbooks_reuse_includes.html
---
What does mean for you: The tasks imported by an `import_role` are now
**always added** to the graph regardless of the usage of
`--include-role-tasks`. This behavior was introduced by #228. Since the
`import*` statements are pre-processed when the playbook is parsed, it's
not trivial to know the tasks are from an `import_role`. I might
eventually change this if people want the same output as the
`include_role` (a dedicated note for the import role as well).
## Example
From this playbook:
```yaml
# tmp.yml
---
- hosts: all
tags:
- play1
roles:
- role: fake_role
tags:
- role_tag
tasks:
- name: Hello world
debug:
msg: Hello world
- name: Import role
import_role:
name: display_some_facts
```
**Before:**
```mermaid
---
title: "ansible-playbook-grapher tmp.yml --renderer mermaid-flowchart"
---
%%{ init: { "flowchart": { "curve": "bumpX" } } }%%
flowchart LR
%% Start of the playbook 'tmp.yml'
playbook_338db25c("tmp.yml")
%% Start of the play 'Play: all (0)'
play_4f34a3fe["Play: all (0)"]
style play_4f34a3fe fill:#bd0faa,color:#ffffff
playbook_338db25c --> |"1"| play_4f34a3fe
linkStyle 0 stroke:#bd0faa,color:#bd0faa
%% Start of the role 'display_some_facts'
play_4f34a3fe --> |"1"| role_ef0c80d6
linkStyle 1 stroke:#bd0faa,color:#bd0faa
role_ef0c80d6(["[role] display_some_facts"])
style role_ef0c80d6 fill:#bd0faa,color:#ffffff,stroke:#bd0faa
%% End of the role 'display_some_facts'
%% End of the play 'Play: all (0)'
%% End of the playbook 'tmp.yml'
```
```mermaid
---
title: "ansible-playbook-grapher tmp.yml --renderer mermaid-flowchart --view --include-role-tasks"
---
%%{ init: { "flowchart": { "curve": "bumpX" } } }%%
flowchart LR
%% Start of the playbook 'tmp.yml'
playbook_78d5da07("tmp.yml")
%% Start of the play 'Play: all (0)'
play_7d50a25e["Play: all (0)"]
style play_7d50a25e fill:#1789b5,color:#ffffff
playbook_78d5da07 --> |"1"| play_7d50a25e
linkStyle 0 stroke:#1789b5,color:#1789b5
%% Start of the role 'display_some_facts'
play_7d50a25e --> |"1"| role_922b8a5b
linkStyle 1 stroke:#1789b5,color:#1789b5
role_922b8a5b(["[role] display_some_facts"])
style role_922b8a5b fill:#1789b5,color:#ffffff,stroke:#1789b5
task_99e90bea[" display_some_facts : ansible_architecture"]
style task_99e90bea stroke:#1789b5,fill:#ffffff
role_922b8a5b --> |"1"| task_99e90bea
linkStyle 2 stroke:#1789b5,color:#1789b5
task_20bff001[" display_some_facts : ansible_date_time"]
style task_20bff001 stroke:#1789b5,fill:#ffffff
role_922b8a5b --> |"2"| task_20bff001
linkStyle 3 stroke:#1789b5,color:#1789b5
task_613c1ada[" display_some_facts : Specific included task for Debian"]
style task_613c1ada stroke:#1789b5,fill:#ffffff
role_922b8a5b --> |"3"| task_613c1ada
linkStyle 4 stroke:#1789b5,color:#1789b5
%% End of the role 'display_some_facts'
task_20de4095["[task] display_some_facts : ansible_architecture"]
style task_20de4095 stroke:#1789b5,fill:#ffffff
play_7d50a25e --> |"2"| task_20de4095
linkStyle 5 stroke:#1789b5,color:#1789b5
task_bfce1de4["[task] display_some_facts : ansible_date_time"]
style task_bfce1de4 stroke:#1789b5,fill:#ffffff
play_7d50a25e --> |"3"| task_bfce1de4
linkStyle 6 stroke:#1789b5,color:#1789b5
task_02381dee["[task] display_some_facts : Specific included task for Debian"]
style task_02381dee stroke:#1789b5,fill:#ffffff
play_7d50a25e --> |"4"| task_02381dee
linkStyle 7 stroke:#1789b5,color:#1789b5
%% End of the play 'Play: all (0)'
%% End of the playbook 'tmp.yml'
```
**After:**
```mermaid
---
title: "ansible-playbook-grapher tmp.yml --renderer mermaid-flowchart"
---
%%{ init: { "flowchart": { "curve": "bumpX" } } }%%
flowchart LR
%% Start of the playbook 'tmp.yml'
playbook_c9ae5c72("tmp.yml")
%% Start of the play 'play #1 (all): 0'
play_60a19b59["play #1 (all): 0"]
style play_60a19b59 stroke:#2332a9,fill:#2332a9,color:#ffffff
playbook_c9ae5c72 --> |"1"| play_60a19b59
linkStyle 0 stroke:#2332a9,color:#2332a9
%% Start of the role '[role] display_some_facts'
play_60a19b59 --> |"1"| role_1f6f5a46
linkStyle 1 stroke:#2332a9,color:#2332a9
role_1f6f5a46(["[role] display_some_facts"])
style role_1f6f5a46 fill:#2332a9,color:#ffffff,stroke:#2332a9
%% End of the role '[role] display_some_facts'
task_3a6c65d1["[task] display_some_facts : ansible_architecture"]
style task_3a6c65d1 stroke:#2332a9,fill:#ffffff
play_60a19b59 --> |"2"| task_3a6c65d1
linkStyle 2 stroke:#2332a9,color:#2332a9
task_166c627a["[task] display_some_facts : ansible_date_time"]
style task_166c627a stroke:#2332a9,fill:#ffffff
play_60a19b59 --> |"3"| task_166c627a
linkStyle 3 stroke:#2332a9,color:#2332a9
task_49929d0c["[task] display_some_facts : Specific included task for Debian"]
style task_49929d0c stroke:#2332a9,fill:#ffffff
play_60a19b59 --> |"4"| task_49929d0c
linkStyle 4 stroke:#2332a9,color:#2332a9
%% End of the play 'play #1 (all): 0'
%% End of the playbook 'tmp.yml'
```
```mermaid
---
title: "ansible-playbook-grapher tmp.yml --renderer mermaid-flowchart --view --include-role-tasks"
---
%%{ init: { "flowchart": { "curve": "bumpX" } } }%%
flowchart LR
%% Start of the playbook 'tmp.yml'
playbook_e3c77447("tmp.yml")
%% Start of the play 'play #1 (all): 0'
play_dcbd8814["play #1 (all): 0"]
style play_dcbd8814 stroke:#9b3181,fill:#9b3181,color:#ffffff
playbook_e3c77447 --> |"1"| play_dcbd8814
linkStyle 0 stroke:#9b3181,color:#9b3181
%% Start of the role '[role] display_some_facts'
play_dcbd8814 --> |"1"| role_91c83316
linkStyle 1 stroke:#9b3181,color:#9b3181
role_91c83316(["[role] display_some_facts"])
style role_91c83316 fill:#9b3181,color:#ffffff,stroke:#9b3181
task_d39cd275["[task] display_some_facts : ansible_architecture"]
style task_d39cd275 stroke:#9b3181,fill:#ffffff
role_91c83316 --> |"1"| task_d39cd275
linkStyle 2 stroke:#9b3181,color:#9b3181
task_0249518a["[task] display_some_facts : ansible_date_time"]
style task_0249518a stroke:#9b3181,fill:#ffffff
role_91c83316 --> |"2"| task_0249518a
linkStyle 3 stroke:#9b3181,color:#9b3181
task_7607b70a["[task] display_some_facts : Specific included task for Debian"]
style task_7607b70a stroke:#9b3181,fill:#ffffff
role_91c83316 --> |"3"| task_7607b70a
linkStyle 4 stroke:#9b3181,color:#9b3181
%% End of the role '[role] display_some_facts'
task_fd594a53["[task] display_some_facts : ansible_architecture"]
style task_fd594a53 stroke:#9b3181,fill:#ffffff
play_dcbd8814 --> |"2"| task_fd594a53
linkStyle 5 stroke:#9b3181,color:#9b3181
task_ead21629["[task] display_some_facts : ansible_date_time"]
style task_ead21629 stroke:#9b3181,fill:#ffffff
play_dcbd8814 --> |"3"| task_ead21629
linkStyle 6 stroke:#9b3181,color:#9b3181
task_30dda673["[task] display_some_facts : Specific included task for Debian"]
style task_30dda673 stroke:#9b3181,fill:#ffffff
play_dcbd8814 --> |"4"| task_30dda673
linkStyle 7 stroke:#9b3181,color:#9b3181
%% End of the play 'play #1 (all): 0'
%% End of the playbook 'tmp.yml'
```
Related to #226
- fix: The tags on the role itself should not be evaluated. Instead,
what we care about is the tasks (they inherit the tags set on the
roles). More info
[here.](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_tags.html#adding-tags-to-roles)
- "Empty roles" are no longer displayed by default. An empty role is a
role with no tasks (after applying the tags filters for example). This
is the same behavior as the option `--hide-empty-plays` but with roles.
**I will eventually drop `--hide-empty-plays` to make this the default
behavior in the future.**
- docs: Add a comparison matrix for the different renderers
- (Internal) Moved some flags out of the parser to the renderer instead.
The whole playbook and all the tasks and roles (except the excluded
ones) are always parsed. The renderer(s) will decide later what do based
on the flags
Related #214
- Add the handlers to the graph with `--show-handlers`. **This is the
initial support for handlers.** They are by default added at the end of
the play and roles only. This doesn't reflect Ansible behavior.
- Changes the shape of the graphviz node to make it consistent with
Mermaid. The tasks will be rectangle instead of `octagon`:
https://graphviz.org/doc/info/shapes.html
- Refactor how the node/task index are computed given we can now add
handlers after all the tasks are parsed.
- Add a new `display_name()` method to the node for a friendly name for
the graph. This removes the of passing the `node_label_prefix` in
multiple places.
- Remove the class **CompositeTasksNode** as it is no longer needed
anymore.
- Remove the play name from the edge going from playbook to the plays.
This was not consistent with the other edges.
## Premise
When running the ansible-playbook-grapher on a project folder, where a
certain role is referenced by a lot of other roles or tasks then the
resulting graph might be confusing especially when grouping the roles by
their names (a lot of arrows crossing each other). So far there was no
option to exclude specific roles from the graph view, so I implemented a
feature for this.
## Changes
- Add entry for the new option ```--exclude-roles``` in README.md
- Add the option and post processing in ```cli.py``` and adjust
```grapher.py``` and ```parser.py``` accordingly
- Update docstrings accordingly
- Add logic to exclude certain roles from being rendered
- Lint project with the corresponding make target
- Add cli and parser tests
- Add methods in ```graph_model.py``` to get all roles of a composite
role (needed for the additional tests)
## Screenshots
without ```--exclude-roles```

with ```--exclude-roles fake_role```

---------
Co-authored-by: David Merkl <dme@ordix.de>
Co-authored-by: Mohamed El Mouctar Haidara <elmhaidara@gmail.com>
## Premise
When running the ansible-playbook-grapher on a huge project folder the
resulting svg or mermaid graph happens to be quiet confusing with all
the task nodes being rendered. So far there was no option to view all
roles (also nested roles) without viewing the corresponding tasks, so I
implemented a feature to do exactly that.
## Changes
- Add entry for the new option ```--only-roles``` in README.md
- Add the option in ```cli.py``` and adjust ```grapher.py``` and
```parser.py``` accordingly
- Update docstrings accordingly
- Add logic to prevent tasks from being added
- Lint project with the corresponding make target
- Add cli and parser tests
## Screenshots
without ```--only-roles```

with ```--only-roles```

---------
Co-authored-by: David Merkl <dme@ordix.de>
Co-authored-by: Mohamed El Mouctar Haidara <elmhaidara@gmail.com>
Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.3.3 to
8.3.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest/releases">pytest's
releases</a>.</em></p>
<blockquote>
<h2>8.3.4</h2>
<h1>pytest 8.3.4 (2024-12-01)</h1>
<h2>Bug fixes</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12592">#12592</a>:
Fixed <code>KeyError</code>{.interpreted-text role="class"}
crash when using <code>--import-mode=importlib</code> in a directory
layout where a directory contains a child directory with the same
name.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12818">#12818</a>:
Assertion rewriting now preserves the source ranges of the original
instructions, making it play well with tools that deal with the
<code>AST</code>, like <a
href="https://github.com/alexmojaki/executing">executing</a>.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12849">#12849</a>:
ANSI escape codes for colored output now handled correctly in
<code>pytest.fail</code>{.interpreted-text role="func"} with
[pytrace=False]{.title-ref}.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/9353">#9353</a>:
<code>pytest.approx</code>{.interpreted-text role="func"} now
uses strict equality when given booleans.</p>
</li>
</ul>
<h2>Improved documentation</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10558">#10558</a>:
Fix ambiguous docstring of
<code>pytest.Config.getoption</code>{.interpreted-text
role="func"}.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10829">#10829</a>:
Improve documentation on the current handling of the
<code>--basetemp</code> option and its lack of retention functionality
(<code>temporary directory location and
retention</code>{.interpreted-text role="ref"}).</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12866">#12866</a>:
Improved cross-references concerning the
<code>recwarn</code>{.interpreted-text role="fixture"}
fixture.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12966">#12966</a>:
Clarify <code>filterwarnings</code>{.interpreted-text
role="ref"} docs on filter precedence/order when using
multiple <code>@pytest.mark.filterwarnings
<pytest.mark.filterwarnings ref></code>{.interpreted-text
role="ref"} marks.</p>
</li>
</ul>
<h2>Contributor-facing changes</h2>
<ul>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12497">#12497</a>:
Fixed two failing pdb-related tests on Python 3.13.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="53f8b4e634"><code>53f8b4e</code></a>
Update pypa/gh-action-pypi-publish to v1.12.2</li>
<li><a
href="98dff36c9d"><code>98dff36</code></a>
Prepare release version 8.3.4</li>
<li><a
href="1b474e221d"><code>1b474e2</code></a>
approx: use exact comparison for bool (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/13013">#13013</a>)</li>
<li><a
href="b541721529"><code>b541721</code></a>
docs: Fix wrong statement about sys.modules with importlib import mode
(<a
href="https://redirect.github.com/pytest-dev/pytest/issues/1298">#1298</a>...</li>
<li><a
href="16cb87b650"><code>16cb87b</code></a>
pytest.fail: fix ANSI escape codes for colored output (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12959">#12959</a>)
(<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12990">#12990</a>)</li>
<li><a
href="be6bc812b0"><code>be6bc81</code></a>
Issue <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12966">#12966</a>
Clarify filterwarnings docs on precedence when using multiple ma...</li>
<li><a
href="7aeb72bbc6"><code>7aeb72b</code></a>
Improve docs on basetemp and retention (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12912">#12912</a>)
(<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12928">#12928</a>)</li>
<li><a
href="c8758414cf"><code>c875841</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12917">#12917</a>
from pytest-dev/patchback/backports/8.3.x/ded1f44e5...</li>
<li><a
href="6502816d97"><code>6502816</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12913">#12913</a>
from jakkdl/dontfailonbadpath</li>
<li><a
href="52135b033f"><code>52135b0</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12885">#12885</a>
from The-Compiler/pdb-py311 (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12887">#12887</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/8.3.3...8.3.4">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Updates the requirements on
[ansible-core](https://github.com/ansible/ansible) to permit the latest
version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/ansible/ansible/releases">ansible-core's
releases</a>.</em></p>
<blockquote>
<h2>v2.18.0</h2>
<h1>Changelog</h1>
<p>See the <a
href="https://github.com/ansible/ansible/blob/v2.18.0/changelogs/CHANGELOG-v2.18.rst">full
changelog</a> for the changes included in this release.</p>
<h1>Release Artifacts</h1>
<ul>
<li>Built Distribution: <a
href="c70341980b/ansible_core-2.18.0-py3-none-any.whl">ansible_core-2.18.0-py3-none-any.whl</a>
- 2212552 bytes
<ul>
<li>d28818df3741d6cd744dab5e4ff9c658daa94ba71c8e15a12dbe9eeab30a658f
(SHA256)</li>
</ul>
</li>
<li>Source Distribution: <a
href="0d5a28caca/ansible_core-2.18.0.tar.gz">ansible_core-2.18.0.tar.gz</a>
- 3064903 bytes
<ul>
<li>87fbebbfe8d961e9b153e84b4438ba3a327dbfdcd4ad05a6065d9ff5d9d02e7b
(SHA256)</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="ec78526b97"><code>ec78526</code></a>
New release v2.18.0 (<a
href="https://redirect.github.com/ansible/ansible/issues/84251">#84251</a>)</li>
<li><a
href="b1366ce965"><code>b1366ce</code></a>
Update Ansible release version to v2.18.0rc2.post0. (<a
href="https://redirect.github.com/ansible/ansible/issues/84198">#84198</a>)</li>
<li><a
href="00031d2d6f"><code>00031d2</code></a>
New release v2.18.0rc2 (<a
href="https://redirect.github.com/ansible/ansible/issues/84193">#84193</a>)</li>
<li><a
href="93c3133c2d"><code>93c3133</code></a>
remove stale changelog entry (<a
href="https://redirect.github.com/ansible/ansible/issues/84187">#84187</a>)</li>
<li><a
href="23f8639a4b"><code>23f8639</code></a>
[stable-2.18] Preserve <code>_ansible_no_log</code> from action result;
fix `include_var...</li>
<li><a
href="3b6de811ab"><code>3b6de81</code></a>
user module avoid conflicts ssh pub key (<a
href="https://redirect.github.com/ansible/ansible/issues/84165">#84165</a>)
(<a
href="https://redirect.github.com/ansible/ansible/issues/84171">#84171</a>)</li>
<li><a
href="cfdafb9bb6"><code>cfdafb9</code></a>
[2.18] Trim <code>selinux_policytype</code> @ integration tests (<a
href="https://redirect.github.com/ansible/ansible/issues/84137">#84137</a>)</li>
<li><a
href="eaec3748c5"><code>eaec374</code></a>
Update Ansible release version to v2.18.0rc1.post0. (<a
href="https://redirect.github.com/ansible/ansible/issues/84124">#84124</a>)</li>
<li><a
href="34ccdfa90a"><code>34ccdfa</code></a>
New release v2.18.0rc1 (<a
href="https://redirect.github.com/ansible/ansible/issues/84122">#84122</a>)</li>
<li><a
href="a3656b2ffb"><code>a3656b2</code></a>
[stable-2.18] facts: Skip path if the distribution path is directory (<a
href="https://redirect.github.com/ansible/ansible/issues/84036">#84036</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/ansible/ansible/compare/v2.16.0...v2.18.0">compare
view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Mohamed El Mouctar HAIDARA <elmhaidara@gmail.com>