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

Allow users to pass a username to defined resource #260

Merged
merged 1 commit into from
Dec 11, 2018
Merged

Conversation

bastelfreak
Copy link
Contributor

From the initial commit in 1fbf6a7:
this allows us to use this defined type as often as we want (which is
the purpose of a defined type). Each usage of it creates an entry in
$user/.ssh/config. This is not a breaking change since you can still use
the resource as before. However, you can now call it multiple types by
setting a unique name for it + providing user => $user as a parameter.

Use case: define a block in each puppet profile you have.

Notice: I needed to bump the concat dependency by a major release, this
means that the next release of this software also should be a major one,
even if the API of this module has no breaking changes.

To use this feature it's required to call the defined resource multiple
times. That requires different names for it. We cannot assume that the
name of the defined resource is always a valid user.

From the initial commit in 1fbf6a7:
this allows us to use this defined type as often as we want (which is
the purpose of a defined type). Each usage of it creates an entry in
$user/.ssh/config. This is not a breaking change since you can still use
the resource as before. However, you can now call it multiple types by
setting a unique name for it + providing user => $user as a parameter.

Use case: define a block in each puppet profile you have.

Notice: I needed to bump the concat dependency by a major release, this
means that the next release of this software also should be a major one,
even if the API of this module has no breaking changes.

To use this feature it's required to call the defined resource multiple
times. That requires different names for it. We cannot assume that the
name of the defined resource is always a valid user.
@bastelfreak
Copy link
Contributor Author

I'm a bit confused why I changed $user to $name in 9aec9b6#diff-7c1e50c5c44243c924ec390fe3a3a151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants