-
Notifications
You must be signed in to change notification settings - Fork 561
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
Document ansible-core architecture #2131
Comments
@webknjaz Your link doesn't explain or document how ansible-core really works... |
related issue #1295 |
fwiw, we have no real documentation about this internal or otherwise. I think some people have little bits and pieces, and some really old whiteboard photos. This is, however, roughly on our TODO list to get something together by June 2025 as part of onboarding documentation we are in need of. I'll attach a photo of a flow diagram we needed a few years back, and a script I created a while ago called https://gist.github.com/sivel/cd0ebabf9fea5401099e7820c58fb0dc |
@sivel Thanks! The flow diagram doesn't make everything clear to me, but it's a start 😃 Would be great if you (as in you, the core team and not you personally) could work a bit on it publish this somewhere. I agree that this would, apart from helping the community at large, be a good thing to have for your onboarding documentation. |
I'm looking for documentation about the architecture and inner workings of ansible-core. I didn't find anything about this. Maybe it exists, in that case it should be made easier to find.
I think knowing more about ansible-core, which is the base of the Ansible ecosystem, would help people to contribute. Not only to ansible-core itself, but also to other projects.
For example, I was looking for a way to cache sessions to a remote API. I learned that each task is a separate process. But I think this isn't documented. At least, I didn't find this anywhere. Someone had to tell me.
I think documenting the inner workings of ansible-core would be helpful to the Ansible community at large. Not everyone has the time to find out by reading (and understanding!) the source code.
The text was updated successfully, but these errors were encountered: