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.

Sign up for GitHub

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

Jump to bottom

Add Foreman 3.8 headline features & upgrade warnings #2434

Merged
merged 1 commit into from
Sep 14, 2023
Merged

Add Foreman 3.8 headline features & upgrade warnings #2434

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions guides/doc-Release_Notes/topics/foreman.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,17 @@
[id="foreman-headline-features"]
== Headline Features

=== Removed installer duplicate parameters

Both `--foreman-logging-layout` and `--puppet-server-foreman-url` are no longer needed.
Copy link
Member Author

Choose a reason for hiding this comment

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

#2432 & #2433 apply this to the docs here.

The logging layout is now derived from the logging type (`--foreman-logging-type`).
The Foreman URL for puppetserver is now read from the Foreman Proxy setting (`--foreman-proxy-foreman-base-url`).
The parameters still exist and can be specified, but the average user shouldn't need it.

[id="foreman-upgrade-warnings"]
== Upgrade Warnings

[id="foreman-deprecations"]
== Deprecations
=== Foreman Redis caching DB changed to 4

Since Foreman 3.6 Foreman can be easily configured to use Redis for caching (using `--foreman-rails-cache-store type:redis`).
Starting Foreman 3.8 this uses DB 4, instead of DB 0, to avoid potential conflicts with other software.