Add a new workflow to help with switching to new client tools channels #4403
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
admd
force-pushed
the
workflow-to-migrate-to-new-client-tools-channels
branch
from
1e855df to
c4dc184
Compare
|
This needs to go in 5.1.1 online docs |
admd
force-pushed
the
workflow-to-migrate-to-new-client-tools-channels
branch
from
c4dc184 to
4701f6d
Compare
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new workflow document that guides administrators through migrating from legacy client tools channels to the new rebranded channels introduced in SUSE Manager 5.1. The workflow provides detailed XML-RPC API examples and Python implementations to automate the migration process.
Key changes:
- Adds comprehensive documentation for synchronizing new client tools channels via API
- Provides step-by-step guidance for updating CLM projects and activation keys to reference new channels
- Includes Python code samples demonstrating automation of the migration process
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
modules/common-workflows/pages/workflow-migrate-to-new-client-tools-channels.adoc
Show resolved
Hide resolved
modules/common-workflows/pages/workflow-migrate-to-new-client-tools-channels.adoc
Show resolved
Hide resolved
|
|
||
| [NOTE] | ||
| ==== | ||
| It is recommend to run your script in dry-run mode first to review the planned changes and test with a single project before applying it to all. |
There was a problem hiding this comment.
Corrected grammar from 'It is recommend' to 'It is recommended'.
Suggested change
| It is recommend to run your script in dry-run mode first to review the planned changes and test with a single project before applying it to all. | |
| It is recommended to run your script in dry-run mode first to review the planned changes and test with a single project before applying it to all. |
nodeg
reviewed
Oct 18, 2025
modules/common-workflows/pages/workflow-migrate-to-new-client-tools-channels.adoc
Show resolved
Hide resolved
0rnela
approved these changes
Oct 20, 2025
This was referenced Oct 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
This PR is adding a new common workflow to help user switch to new client tools channels
Target branches
ifevalstatements are needed to publish it for certain products only.Backport targets (edit as needed):
Links