The ansible.networking.network_cli connection plugin uses the
ansible.netcommon.libssh connection plugin or falls back to
ansible.builtin.paramiko.
The ansible.builtin.paramiko connection no longer uses the variable
'ansible_ssh_common_args' to configure connecting via a jumphost, and
now requires the variable 'ansible_paramiko_proxy_command'.
This variable is also supported by ansible.netcommon.libssh >= 2.2.0
(in addition to ansible_libssh_proxy_command).
Also fix example for ansible.netcommon.netconf, which never appears to
have never supported 'ansible_ssh_common_args', but does support
'ansible_paramiko_proxy_command' and 'ansible_netconf_proxy_command'.
* Build and deploy from the devel branch once a week, preferably at the start of the week
Fixes#2049
* Base Fixups
* Change to Daily
* Fixes#2049 & #2050
* After some testing, this example works otherwise unmondified if we bump this to fedora 40 (41 and 42 had other failures and would require additional investigation/modification)
* Schedule doc builds for devel and latest
Fixes#2049 and #2050
(cherry picked from commit f6a8f2e73beb346213b071f21bf09e78a7c6fff9)
* rename workflows and rm inputs with defaults
(cherry picked from commit 883a23d1dfcbc954b9edb0e8ba17ac590c9fcdd5)
* add single quotes for consistency
(cherry picked from commit 835340d1de39c29a00e7ee637f02fc456ef36ad6)
* update workflow names
(cherry picked from commit bd29aaa23b666086d887eb4a7e8380171c1b9f17)
* Revert "After some testing, this example works otherwise unmondified if we bump this to fedora 40 (41 and 42 had other failures and would require additional investigation/modification)"
This reverts commit a6b378c787.
* Cleanup legacy files from rename
---------
Co-authored-by: Don Naro <dnaro@redhat.com>
* porting_guide_core_2.19.rst: add clatifications on the required non-string key conversion
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Don Naro <dnaro@redhat.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Don Naro <dnaro@redhat.com>
* Add an example how to convert
* Add example
* Change example
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
---------
Co-authored-by: Don Naro <dnaro@redhat.com>
Co-authored-by: Matt Clay <matt@mystile.com>
* update core support matrix 2.19
* fix formatting and GA date
* Update docs/docsite/rst/reference_appendices/release_and_maintenance.rst
Co-authored-by: Matt Martz <matt@sivel.net>
* Update docs/docsite/rst/reference_appendices/release_and_maintenance.rst
Co-authored-by: Maxwell G <maxwell@gtmx.me>
* add reference to changelog
---------
Co-authored-by: Matt Martz <matt@sivel.net>
Co-authored-by: Maxwell G <maxwell@gtmx.me>
We should use the official action for retrieving the token to use for
the issue/PR triage and dependency update workflows instead of the one
we were using before.
This makes slight changes to the handling of universal lockfiles. These
were regenerated with `nox -e pip-compile -- --no-upgrade` to keep the
versions the same but adapt to the new way uv simplifies environment
markers.
The lockfiles for the pip-compile session itself were never updated
because I forgot to add them to the update workflow.
The pr_labeler lockfile is still excluded, but that's intentional for
now. I'd like this to happen manually or as part of a separate automated
workflow for now, as there's no automated tests for that script as of
yet, so I don't want it to randomly break when we merge these general
pip-compile-dev PRs.
Previously, this only would create a PR when the branch was newly
created earlier in the workflow (assuming that branches would be deleted
once the previous dependency update PR was merged), but it was possible
for the branch to already exist but not have a PR open against it.
This uses the Github API to properly check whether a PR already exists.
