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

Add ability to configure custom_trusted_oid_mapping.yaml #603

Conversation

baurmatt
Copy link
Contributor

@baurmatt baurmatt commented Jun 25, 2018

This commit adds support to configure the
$confdir/custom_trusted_oid_mapping.yaml as described in
https://puppet.com/docs/puppet/5.5/config_file_oid_map.html.

Fixes GH-602

@theforeman-bot

This comment has been minimized.

@theforeman-bot

This comment has been minimized.

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

I've changed the #issue to GH-issue in the opening message so it doesn't conflict with our issue tracker. Could you do the same in the commit message?

@@ -182,7 +182,7 @@
# $environment:: Default environment of the Puppet agent
#
# $agent_additional_settings:: A hash of additional agent settings.
# Example: {stringify_facts => true}
# Example: {stringify_facts => true}
Copy link
Member

Choose a reason for hiding this comment

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

Could you revert this change and other whitespace only changes?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done! Sorry! :/ Are the whitespace changes in server.pp ok?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, indenting is no problem.

@@ -0,0 +1,4 @@
type Puppet::Custom_trusted_oid_mapping = Hash[String, Struct[{
Copy link
Member

Choose a reason for hiding this comment

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

We have a bug in our installer that it currently doesn't handle multi line types because it does incorrect manual parsing. We should be fixing it but in the short term I wonder if we should put it on a single line.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure!

end

it 'should have a configured custom_trusted_oid_mapping.yaml' do
should contain_file("#{confdir}/custom_trusted_oid_mapping.yaml").
Copy link
Member

Choose a reason for hiding this comment

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

We have a verify_exact_contents helper which might be easier to use.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is really helpful, thanks! :)

@theforeman-bot

This comment has been minimized.

@theforeman-bot

This comment has been minimized.

@theforeman-bot

This comment has been minimized.

@theforeman-bot

This comment has been minimized.

This commit adds support to configure the
$confdir/custom_trusted_oid_mapping.yaml as described in
https://puppet.com/docs/puppet/5.5/config_file_oid_map.html.

Fixes theforemanGH-602.
@theforeman-bot

This comment has been minimized.

@baurmatt baurmatt force-pushed the feature/manage_custom_trusted_oid_mapping.yaml branch from 225171c to 7acde39 Compare June 25, 2018 14:07
@theforeman-bot

This comment has been minimized.

@baurmatt
Copy link
Contributor Author

Fixed review comments, thanks! :)

@ekohl ekohl merged commit f99fa45 into theforeman:master Sep 12, 2018
@ekohl
Copy link
Member

ekohl commented Sep 12, 2018

Thanks!

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.

3 participants