Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency ansible to v11 #1214

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ggrossetie
Copy link
Collaborator

@ggrossetie ggrossetie commented Jan 27, 2025

This PR contains the following updates:

Package Update Change
ansible (source) major ==9.13.0 -> ==11.3.0

Release Notes

ansible-community/ansible-build-data (ansible)

v11.3.0

Compare Source

v11.2.0

Compare Source

v11.1.0

Compare Source

v11.0.0

Compare Source

v10.7.0

Compare Source

v10.6.0

Compare Source

v10.5.0

Compare Source

v10.4.0

Compare Source

v10.3.0

Compare Source

v10.2.0

Compare Source

v10.1.0

Compare Source

v10.0.1

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

netlify bot commented Jan 27, 2025

Deploy Preview for stylo-docs canceled.

Name Link
🔨 Latest commit 84a760e
🔍 Latest deploy log https://app.netlify.com/sites/stylo-docs/deploys/67bf2324126fc10008c593ac

@ggrossetie ggrossetie force-pushed the renovate/major-ansible-dependencies branch from 481646c to 50da7f3 Compare January 29, 2025 02:32
@ggrossetie ggrossetie force-pushed the renovate/major-ansible-dependencies branch from 50da7f3 to 1d67c79 Compare February 26, 2025 02:36
@ggrossetie
Copy link
Collaborator Author

Apparemment, il faut Python >=3.11

ERROR: No matching distribution found for ansible==11.3.0

@thom4parisot
Copy link
Member

Sur la machine de destination, ou sur le runner GitHub ?

@ggrossetie
Copy link
Collaborator Author

Sur la machine de destination, ou sur le runner GitHub ?

Sur le runner GitHub mais sur la machine de destination il faut Python >= 3.7 sinon on a cette erreur:

SyntaxError: future feature annotations is not defined

@ggrossetie
Copy link
Collaborator Author

Le déploiement sur stylo-dev est passé. J'ai fais les opérations suivantes sur la machine cible :

sudo apt update
sudo apt install python3.8 
sudo update-alternatives  --set python3  /usr/bin/python3.8
sudo update-alternatives  --set python  /usr/bin/python3.8

cd /usr/lib/python3/dist-packages/
sudo ln -s apt_pkg.cpython-36m-x86_64-linux-gnu.so apt_pkg.so
sudo ln -s apt_inst.cpython-36m-x86_64-linux-gnu.so apt_inst.so

@thom4parisot
Copy link
Member

On peut demander cette version de python dans le playbook ansible ?

(je me demande s'il est possible de scripter une instance fraiche avec ansible, dans ce playbook ou un autre)

@ggrossetie
Copy link
Collaborator Author

On peut demander cette version de python dans le playbook ansible ?

D'après ce que je vois en ligne, il serait possible d'utiliser un playbook avec le module "raw" (https://docs.ansible.com/ansible/latest/collections/ansible/builtin/raw_module.html) afin d'installer Python. Pas sûr que ça soit très rentable comme automatisation.

Surtout que sur les nouvelles VMs (Ubuntu 24.04), la version de Python installée par défaut est 3.12 donc on aura pas de soucis (et on aura pas à jouer avec les update-alternatives et les liens symboliques)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants