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

Introduce foreman::settings_fragment #1016

Merged
merged 1 commit into from
Feb 4, 2022

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Jan 10, 2022

This provides a stable API to provide fragments to settings.yaml. This means we don't need to create parameters for every single setting.

@fe80
Copy link

fe80 commented Jan 10, 2022

It's possible to create a create_resource for manage that with hiera ? And maybe a validation with a custom type (or this is too much)?

I can look that in different pull request

@ekohl
Copy link
Member Author

ekohl commented Jan 11, 2022

I'd prefer that in a separate PR. I can't find the bug right now, but note we have some issues in our installer parsing types that span multiple lines. That is likely to show up there.

@ekohl ekohl force-pushed the settings_fragment-api branch from f7afe81 to 785677f Compare February 1, 2022 17:44
@ekohl ekohl mentioned this pull request Feb 3, 2022
order: '42',
}
end

Copy link
Member

Choose a reason for hiding this comment

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

should we add a:

it { is_expected.to compile.with_all_deps }

?

This provides a stable API to provide fragments to settings.yaml. This
means we don't need to create parameters for every single setting.
@ekohl ekohl force-pushed the settings_fragment-api branch from 785677f to d4ee7d4 Compare February 3, 2022 16:19
@ekohl ekohl merged commit 948d2a9 into theforeman:master Feb 4, 2022
@ekohl ekohl deleted the settings_fragment-api branch February 4, 2022 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants