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

use name instead of source for installing collection dir requirements #2259

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

s-hertel
Copy link
Contributor

@s-hertel s-hertel commented Dec 5, 2024

I should have caught this before approving the PR that added these examples.

When the dependency resolver was added to ansible-galaxy in 2.12, it inadvertently overloaded the source collection requirement field, which was previously only able to be a URL to a galaxy server. Now it is sort of an alias to name in some situations, and it's a bug because we had specifically discussed not unifying role src vs collection source for requirements, because although it's unfortunate that they're similarly named but completely different features (one is a URL to a role, the other is a URL galaxy server), it was outside of the scope of that PR (and at the time of discussion, I was under the impression we would want to make the role syntax more like collections though - not the other way around).

@s-hertel s-hertel changed the title document using name instead of source for installing collection requirements using name instead of source for installing collection dir requirements Dec 5, 2024
@s-hertel s-hertel changed the title using name instead of source for installing collection dir requirements use name instead of source for installing collection dir requirements Dec 5, 2024
@samccann samccann requested a review from oraNod December 10, 2024 15:45
@samccann samccann added backport-2.16 Automatically create a backport for the stable-2.16 branch backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch labels Dec 10, 2024
Copy link
Contributor

@oraNod oraNod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @s-hertel

@oraNod oraNod merged commit 2e09b53 into ansible:devel Dec 11, 2024
11 checks passed
Copy link

patchback bot commented Dec 11, 2024

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/2e09b533cea028e717c2ce3e05f00cf7aee23a0b/pr-2259

Backported as #2285

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Copy link

patchback bot commented Dec 11, 2024

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/2e09b533cea028e717c2ce3e05f00cf7aee23a0b/pr-2259

Backported as #2286

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Copy link

patchback bot commented Dec 11, 2024

Backport to stable-2.18: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.18/2e09b533cea028e717c2ce3e05f00cf7aee23a0b/pr-2259

Backported as #2287

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Dec 11, 2024
oraNod pushed a commit that referenced this pull request Dec 11, 2024
…ories (#2259) (#2287)

(cherry picked from commit 2e09b53)

Co-authored-by: Sloane Hertel <[email protected]>
oraNod pushed a commit that referenced this pull request Dec 11, 2024
…ories (#2259) (#2286)

(cherry picked from commit 2e09b53)

Co-authored-by: Sloane Hertel <[email protected]>
oraNod pushed a commit that referenced this pull request Dec 11, 2024
…ories (#2259) (#2285)

(cherry picked from commit 2e09b53)

Co-authored-by: Sloane Hertel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-2.16 Automatically create a backport for the stable-2.16 branch backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants