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
fix installing collections from git repos that contain MANIFEST.json #79808
fix installing collections from git repos that contain MANIFEST.json #79808
Conversation
…ng MANIFEST.json changelog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. Should we add a test?
d2eabf0
to
ded17a0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approving. LGTM
I thought we had established that to install from git |
@bcoca That was the plan, but it changed in 2.11 with the feature of installing collections from non-git dir/subdirs. Now SCM collections are just a wrapper collection that has a dir or subdirs dependency. We would have needed to make a distinction between directories that originate from SCM collections and other directories, and that was vetoed at the time. |
da0b114
to
283511f
Compare
changelogs/fragments/ansible-galaxy-install-git-src-manifest.yml
Outdated
Show resolved
Hide resolved
…nsible#79808) * add null 'manifest' key to metadata for git repo collections containing MANIFEST.json changelog * set to Sentinel instead of None * Test installing a collection in a git repo that contains a MANIFEST.json * fix test * Update changelogs/fragments/ansible-galaxy-install-git-src-manifest.yml (cherry picked from commit 321848e)
SUMMARY
Fixes #79796
As of 595413d, collections in git repos can contain a galaxy.yml or MANIFEST.json (just like non-git repo directories).
ISSUE TYPE
COMPONENT NAME
ansible-galaxy collection install