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 base_name parameter to apt::setting #442

Merged
merged 1 commit into from
Feb 25, 2015

Conversation

underscorgan
Copy link

This allows you to work around duplicate resource issues when you have
settings of different types with the same name. When the files are built
it is path/${priority}${base_name}${extension}.

@@ -1,5 +1,6 @@
define apt::setting (
$setting_type,
$base_name = $name,
Copy link

Choose a reason for hiding this comment

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

We should use $title here as per https://docs.puppetlabs.com/puppet/latest/reference/lang_defined_types.html#title-and-name

$name defaults to the value of $title, but users can optionally specify a different value when they declare an instance. This is only useful for mimicking the behavior of a resource with a namevar, which is usually unnecessary. If you are wondering whether to use $name or $title, use $title.

@daenney daenney assigned underscorgan and unassigned daenney Feb 25, 2015
This allows you to work around duplicate resource issues when you have
settings of different types with the same name. When the files are built
it is path/${priority}${base_name}${extension}.
@underscorgan underscorgan assigned daenney and unassigned underscorgan Feb 25, 2015
daenney added a commit that referenced this pull request Feb 25, 2015
Add base_name parameter to apt::setting
@daenney daenney merged commit 1c0c6f1 into puppetlabs:next Feb 25, 2015
@underscorgan underscorgan deleted the add_base_name branch May 8, 2015 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants