Fixes #36597 - Rename 'Change content source' job template #10652
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes introduced in this pull request?
The user was confused because running the job template on the host didn't change the host's content source. In actuality, it updates subscription-manager configuration on the host based on the host's current content source. It's meant to only be run just after changing the content source on the server, as part of the 'Change Content Source' feature.
So, the changes here are
Change content source
toConfigure host for new content source
. This reflects what the job template actually does. Includes a DB migration similar to https://github.com/theforeman/foreman/blob/develop/db/migrate/20220204155632_rename_job_report_template.rb (thanks for the tip @ianballou)change_content_source
toconfigure_host_for_new_content_source
Considerations taken when implementing this change?
I didn't update the name of the remote execution feature, since that would require a code change in foreman_remote_execution.
What are the testing steps for this pull request?
Run migrations:
Run seeds and restart the server:
Test the following: