-
Notifications
You must be signed in to change notification settings - Fork 108
Add modules to upload content to Deb repositories #4531
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
Merged
maximiliankolb
merged 1 commit into
theforeman:master
from
ATIX-AG:uploading_to_deb_repositories
Jan 14, 2026
+51
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
27 changes: 27 additions & 0 deletions
27
guides/common/modules/proc_uploading-content-to-deb-repositories-by-using-cli.adoc
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| :_mod-docs-content-type: PROCEDURE | ||
|
|
||
| [id="uploading-content-to-deb-repositories-by-using-cli"] | ||
| = Uploading content to Deb repositories by using Hammer CLI | ||
|
|
||
| [role="_abstract"] | ||
| You can upload individual Deb packages to Deb repositories by using Hammer CLI. | ||
maximiliankolb marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| Do not upload packages to a repository if you have set the *Upstream URL*. | ||
|
|
||
| .Procedure | ||
| * Upload a Deb package: | ||
| + | ||
| [options="nowrap" subs="+quotes,verbatim"] | ||
| ---- | ||
| $ hammer repository upload-content \ | ||
| --content-type deb \ | ||
| --id _My_Repository_ID_ \ | ||
| --path _/path/to/example-package.deb_ | ||
| ---- | ||
|
|
||
| .Verification | ||
| * Verify that your Deb repository contains the Deb package that you have uploaded: | ||
| + | ||
| [options="nowrap" subs="+quotes,verbatim"] | ||
| ---- | ||
| $ hammer deb list --repository-id _My_Repository_ID_ | ||
| ---- | ||
18 changes: 18 additions & 0 deletions
18
.../common/modules/proc_uploading-content-to-deb-repositories-by-using-web-ui.adoc
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| :_mod-docs-content-type: PROCEDURE | ||
|
|
||
| [id="uploading-content-to-deb-repositories-by-using-web-ui"] | ||
| = Uploading content to Deb repositories by using {ProjectWebUI} | ||
|
|
||
| [role="_abstract"] | ||
| You can upload individual Deb packages to Deb repositories by using {ProjectWebUI}. | ||
|
|
||
| .Procedure | ||
| . In the {ProjectWebUI}, navigate to *Content* > *Products*. | ||
| . Select your {customproduct}. | ||
| . Select the Deb repository that you want to upload packages to. | ||
maximiliankolb marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| Do not upload packages to a repository if you have set the *Upstream URL*. | ||
| . Under *Upload Package*, click *Browse...* and select the Deb package that you want to upload. | ||
| . Click *Upload*. | ||
|
|
||
| .Verification | ||
| * To view all Deb packages in this repository, click the number next to *Packages* under *Content Counts*. | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional (because we're not there with the other abstracts yet and it wouldn't be fair to require this at the moment): Ideally, an abstract should also clarify the use case: when and why a user might want to follow the procedure, not just what the procedure does.
For example
when: Is the "individual packages" part important here? Is this what distinguishes this procedure from other procedures in the guide? When would a user want to upload an individual package?Or
why: What will happen when the package will be uploaded? Can we explicitly specify that the package will then be available for hosts?