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

[ansible] Evaluate a dedicated Ansible collection target type #72

Open
sureshjoshi opened this issue Jun 21, 2022 · 2 comments
Open

[ansible] Evaluate a dedicated Ansible collection target type #72

sureshjoshi opened this issue Jun 21, 2022 · 2 comments

Comments

@sureshjoshi
Copy link
Owner

No description provided.

@Eric-Arellano
Copy link

What would this entail? A target generator like python_sources -> python_source?

@sureshjoshi
Copy link
Owner Author

@lilatomic had a lot of good ideas about this. Essentially, as roles/collections have a dedicated folder structure - determining the source root and then using that folder type to figure out what is part of that collection (and role, and whatever else) seems like a reasonable idea.

That might involve a generator to enumerate all the files, or maybe some resources/files targets in addition to code. Not sure exactly, but for now, a clever glob would work.

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

No branches or pull requests

2 participants