On Tue, Apr 18, 2023 at 9:38 PM for tan <[email protected]> wrote:
>
> Thats great.  And could likely use this as is , at times,  sometimes... but 
> the liklihood this gz bundle is exactly as we need it to be each time we need 
> it, is not likely.

That's why pypi.org publishes these with release numbers, and for most
projects in the open source world the tag numbers are a reference to a
particular git commit.

I'm going to discourage you from trying to outsmart the people who
publish software releases for open source projects. You can spend a
lot of billable hours trying for additional layers of assurance, but
those additional layers often create their own instability.

> What would be the recipe to creat this so can add delete chane parts as 
> needed.

Don't use the "ansible" package. Use a stable "ansible-core", which is
where the ansible software really lives and is maintained, and use the
"ansible-galaxy" command with some scripting to insall specific
modules from the galaxy colledtions, if and only if needed.


> I scrounged up this skeleton to create a remote installable archive  to 
> upgrade ancible on remote host.  Would executing something similar to this as 
> a playbook be part of how this gz is created ? Please comment. Thx

I'll suggest that you're re-inventing the wheel. Have some fun playing
with it if you like, strongly consider using only the packaged
"ansible-core" for your distribution, and install modules from the
ansible galaxy collections only as needed. You can get finicky about
managing *those* in a mirrored or replicated location if you feel the
need. But if you're already using ansible, why not let it do its job,
eat your own dog food, and use ansible to update the additional
modules?

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAOCN9rwFGN67F-VqEPSQpkpAwJBfDyc1XFAFzmgfwOXWKgr13A%40mail.gmail.com.

Reply via email to