Skip to content

Add foremanctl commands for IoP - #5096

Open
Lennonka wants to merge 4 commits into
theforeman:masterfrom
Lennonka:add-foremanctl-to-enable-iop
Open

Add foremanctl commands for IoP#5096
Lennonka wants to merge 4 commits into
theforeman:masterfrom
Lennonka:add-foremanctl-to-enable-iop

Conversation

@Lennonka

@Lennonka Lennonka commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

What changes are you introducing?

Adding foremanctl commands for IoP in containerized Foreman:

  • enabling IoP
  • disabling IoP
  • setting the logging levels of IoP

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Containerization

SAT-40194

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

  • Assisted by AI
  • Needs to be tech reviewed and tested

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into: N/A

@github-actions github-actions Bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Jul 22, 2026
----
endif::[]
ifdef::containerized[]
.. Create a `config.yml` file that includes the following logging levels together with the required IOP core engine configuration:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would either say "IoP" or use the attribute https://github.com/theforeman/foreman-documentation/blob/master/guides/common/attributes-base.adoc#L174

same applies to line 76.

Comment thread guides/common/modules/proc_updating-server.adoc Outdated
----
# {foreman-installer} --enable-iop
ifndef::containerized[# {foreman-installer} --enable-iop]
ifdef::containerized[# {foremanctl} deploy --add-feature iop]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if it's the same like line 24, then maybe a different structure is better because users do not need to know if they used IoP before.

@Lennonka

Copy link
Copy Markdown
Contributor Author

@maximiliankolb Thanks a lot for your notes! I will need a tech review first because it will decide how to proceed further.

@Lennonka
Lennonka force-pushed the add-foremanctl-to-enable-iop branch 2 times, most recently from 82569d4 to 2040262 Compare July 23, 2026 14:58
"":
level: "DEBUG"
----
.. Replace the `iop-core-engine-config-yml` Podman secret:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't love this as a procedure that we are telling users to do. @vkrizan Do you think we should add this as a logging option in foremanctl ?

@Lennonka
Lennonka force-pushed the add-foremanctl-to-enable-iop branch 2 times, most recently from 0dfcb0c to 4986cc4 Compare July 28, 2026 14:54
@Lennonka
Lennonka force-pushed the add-foremanctl-to-enable-iop branch from 4986cc4 to 314c2a9 Compare July 28, 2026 15:10
Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants