Repository navigation
Document the current web UI steps for importing a subscription manifest - #5435
Open
Satellite-RedHat wants to merge 1 commit into
Open
Satellite-RedHat wants to merge 1 commit into
Satellite-RedHat wants to merge 1 commit into
Conversation
The Subscriptions page opens the manifest window from Import a Manifest on a fresh installation, and selecting the .zip file starts the import. Co-authored-by: Cursor <cursoragent@cursor.com>
github-actions
Bot
added
Needs tech review
Contributor
AkshayGadhaveRH
suggested changes
Oct 7, 2026
Comment on lines
+22
to
+23
|
|
||
| The import starts when you select the `.zip` file. |
Contributor
There was a problem hiding this comment.
Suggested change
| The import starts when you select the `.zip` file. |
This seems redundant.
| . In the *Manage Manifest* window, click *Choose File*. | ||
| . Navigate to the location that contains the Red{nbsp}Hat subscription manifest file, then click *Open*. | ||
| . If no manifest is imported, click *Import a Manifest*. | ||
| To import a manifest when one is already present, open the actions menu and click *Manage manifest*. |
Contributor
There was a problem hiding this comment.
Suggested change
| To import a manifest when one is already present, open the actions menu and click *Manage manifest*. | |
| . Click *Import a Manifest*. |
I think there is a bit of a problem here as the next step only applies for users who are following the Manage Manifest method.
I am wondering if we can keep this procedure only for users who are uploading a new manifest i.e. the empty state action, and update the procedure in proc_updating-and-refreshing-red-hat-subscription-manifests.adoc.
This module is rendered only for the Managing Content guide and I believe this information only belongs in that guide, and not in the Installation guides.
pr-processor
Bot
added
Waiting on contributor
Comment on lines
+17
to
+18
| . If no manifest is imported, click *Import a Manifest*. | ||
| To import a manifest when one is already present, open the actions menu and click *Manage manifest*. |
Contributor
There was a problem hiding this comment.
another issue: If line 17 starts with "If ...", then users might not continue to read line 18. So IMO line 18 should also be a step. Maybe use two if statements:
Suggested change
| . If no manifest is imported, click *Import a Manifest*. | |
| To import a manifest when one is already present, open the actions menu and click *Manage manifest*. | |
| . Import your manifest: | |
| * If no manifest is imported, click *Import a Manifest*. | |
| * If you already have a manifest imported to {Project}, open the actions menu and click *Manage manifest*. |
Maybe it also makes sense to move line 19 under the second unordered list item.
This branch has not been deployed
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
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.
What changes are you introducing?
Update the shared web UI procedure for importing a Red Hat subscription manifest.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
The Subscriptions page no longer uses Manage Manifest, Choose File, and Open. On a fresh installation, for both connected and disconnected servers, the empty state action is Import a Manifest. When a manifest is already imported, the same window is available from the actions menu as Manage manifest. In the Manage Manifest window, on the Manifest tab, click Upload and select the manifest .zip. The import starts when the file is selected.
This module is included by the connected install guide, the disconnected install guide, and Managing content, so one change updates all three.
Downstream tracking: https://redhat.atlassian.net/browse/SAT-51920
The new file control is in current Katello. Katello 4.21 and earlier still use a file input, so this should not be cherry-picked to those branches.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
The recommended path is Import a Manifest during installation. The actions-menu path is included because Managing content uses the same module after a manifest already exists.
Contributor checklists
Please cherry-pick my commits into: