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

redhat_manifest - set default quantity to 1 #1499

Merged
merged 1 commit into from
Oct 26, 2022

Conversation

evgeni
Copy link
Member

@evgeni evgeni commented Oct 12, 2022

The code decides whether subs need to be attached or not by the presence of the pool_id parameter. However, to be able to actually attach a pool, one also needs to pass the quantity.

We could document that and set a required_together property, or do the sensible thing and just default the quantity to 1, which is a sane default in the days of SCA where we need to attach a sub to make Katello aware of the fact that we have access to said content, but otherwise don't need the correct amount of subs attached for providing them to clients.

The code decides whether subs need to be attached or not by the presence
of the `pool_id` parameter. However, to be able to actually attach a
pool, one also needs to pass the quantity.

We could document that and set a `required_together` property, or do the
sensible thing and just default the `quantity` to 1, which is a sane
default in the days of SCA where we need to attach a sub to make Katello
aware of the fact that we have access to said content, but otherwise
don't need the *correct amount* of subs attached for providing them to
clients.
@ikke-t
Copy link

ikke-t commented Oct 12, 2022

I second the default of one. I was thinking to ask you this, but you already did it.

@sideangleside
Copy link

+1 from me as well, especially given that #1494 will make the default manifest mode org_environment

@evgeni evgeni merged commit 6c8d41b into theforeman:develop Oct 26, 2022
@evgeni evgeni deleted the pool-default-quantity branch October 26, 2022 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants