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

Update remote rh-certified default url #2032

Merged
merged 1 commit into from Jan 19, 2024
Merged

Conversation

drodowic
Copy link
Collaborator

What is this PR doing:

  • Updates the remote rh-certified default url

AAP-15623

Reviewers must know:

PR Author & Reviewers: Keep or remove backport labels per Backporting Guidelines
Reviewers: Look for sound code, no code smells, docs & test coverage
Merger: When merging, include the Jira issue link in the squashed commit

@github-actions github-actions bot added backport-4.2 This PR should be backported to stable-4.2 (1.2) backport-4.4 This PR should be backported to stable-4.4 (2.1) backport-4.5 This PR should be backported to stable-4.5 (2.2) backport-4.6 This PR should be backported to stable-4.6 (2.3) backport-4.7 This PR should be backported to stable-4.7 (2.4) backport-4.8 This PR should be backported to stable-4.8 (2.4) backport-4.9 This PR should be backported to stable-4.9 (2.4) labels Jan 15, 2024
@jctanner
Copy link
Contributor

Are we backporting this or should those labels be removed?

Copy link
Contributor

@jctanner jctanner left a comment

Choose a reason for hiding this comment

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

If a system has already run this migration, it won't run it again if the file changed. I think it'd be better to make a new migration file which is sure to be run.

@drodowic
Copy link
Collaborator Author

If a system has already run this migration, it won't run it again if the file changed. I think it'd be better to make a new migration file which is sure to be run.

The intent in modifying an existing migration is so that only new installations will get the updated URL so that we don't impact customers who might have already modified it.

@jctanner
Copy link
Contributor

If a system has already run this migration, it won't run it again if the file changed. I think it'd be better to make a new migration file which is sure to be run.

The intent in modifying an existing migration is so that only new installations will get the updated URL so that we don't impact customers who might have already modified it.

A new migration file can do a conditional update by checking the current value.

@jctanner
Copy link
Contributor

With the new migration file, we can remove the change in the old file right? Also, should the backport labels be removed?

@drodowic drodowic removed backport-4.2 This PR should be backported to stable-4.2 (1.2) backport-4.4 This PR should be backported to stable-4.4 (2.1) backport-4.5 This PR should be backported to stable-4.5 (2.2) backport-4.6 This PR should be backported to stable-4.6 (2.3) backport-4.7 This PR should be backported to stable-4.7 (2.4) backport-4.8 This PR should be backported to stable-4.8 (2.4) backport-4.9 This PR should be backported to stable-4.9 (2.4) labels Jan 17, 2024
@drodowic drodowic merged commit 5b846b5 into ansible:master Jan 19, 2024
20 of 21 checks passed
@drodowic drodowic deleted the AAP-15623 branch January 19, 2024 15:03
@rochacbruno rochacbruno added the backport-4.9 This PR should be backported to stable-4.9 (2.4) label Feb 21, 2024
Copy link

patchback bot commented Feb 21, 2024

Backport to stable-4.9: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-4.9/5b846b5c17a01137e04dfc34aad2bf9404d9859d/pr-2032

Backported as #2077

🤖 @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 Feb 21, 2024
AAP-15623

(cherry picked from commit 5b846b5)
rochacbruno added a commit to rochacbruno/galaxy_ng that referenced this pull request Feb 21, 2024
Add /content/published to the default URL when setting up the
default remotes.

This has been fix on ansible#2032 but that PR not backported.

This PR changes the original migration, so fresh installs gets the new URL
and existing systems are not affected

This must be backported to 4.9.z

No-Issue
Related: AAH-2836
rochacbruno added a commit to rochacbruno/galaxy_ng that referenced this pull request Feb 29, 2024
Add /content/published to the default URL when setting up the
default remotes.

This has been fix on ansible#2032 but that PR not backported.

This PR changes the original migration, so fresh installs gets the new URL
and existing systems are not affected

This must be backported to 4.9.z

No-Issue
Related: AAH-2836
rochacbruno added a commit that referenced this pull request Feb 29, 2024
Add /content/published to the default URL when setting up the
default remotes.

This has been fix on #2032 but that PR not backported.

This PR changes the original migration, so fresh installs gets the new URL
and existing systems are not affected

This must be backported to 4.9.z

No-Issue
Related: AAH-2836
patchback bot pushed a commit that referenced this pull request Feb 29, 2024
Add /content/published to the default URL when setting up the
default remotes.

This has been fix on #2032 but that PR not backported.

This PR changes the original migration, so fresh installs gets the new URL
and existing systems are not affected

This must be backported to 4.9.z

No-Issue
Related: AAH-2836

(cherry picked from commit 5d56bdd)
rochacbruno added a commit that referenced this pull request Mar 1, 2024
… the correct URL for rh-certified (#2089)

fix: Fresh installs must get the correct URL for rh-certified (#2078)

Add /content/published to the default URL when setting up the
default remotes.

This has been fix on #2032 but that PR not backported.

This PR changes the original migration, so fresh installs gets the new URL
and existing systems are not affected

This must be backported to 4.9.z

No-Issue
Related: AAH-2836

(cherry picked from commit 5d56bdd)

Co-authored-by: Bruno Rocha <rochacbruno@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-4.9 This PR should be backported to stable-4.9 (2.4)
Projects
None yet
3 participants