Jira (PUP-3496) Ability to set default provider or require `provider` to be set

[Jeremy Barlow (JIRA)]

Jeremy Barlow updated an issue

Puppet / PUP-3496 Ability to set default provider or require `provider` to be set Change By: Jeremy Barlow Labels: help_wanted triaged Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-3496 Ability to set default provider or require `provider` to be set

Change By: Moses Mendoza Labels: help_wanted  triaged

Add Comment

[Jorie Tappa (JIRA)]

Jorie Tappa updated an issue

Puppet / PUP-3496 Ability to set default provider or require `provider` to be set

Change By: Jorie Tappa Team: Coremunity

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-3496

Re: Ability to set default provider or require `provider` to be set One way to implement 'always default' is to confine based on a fact and pass a regex as the value: defaultfor :osfamily => /.*/ The above is a bit of a hack. I can imagine having a DSL method something like always_defaultfor that causes default_match to always return true. Also as an aside, we added the ability to specify notdefaultfor. Several service providers take advantage of that since the default provider changes based on OS version, eg upstart vs systemd.

Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)