Jira (PUP-8349) SPIKE scheduled_task : should we deprecate scheduled_task resource?

1 view
Skip to first unread message

Erick Banks (JIRA)

unread,
Jan 17, 2018, 2:39:04 PM1/17/18
to puppe...@googlegroups.com
Erick Banks updated an issue
 
Puppet / Task PUP-8349
SPIKE scheduled_task : should we deprecate scheduled_task resource?
Change By: Erick Banks
Summary: SPIKE scheduled_task :  Deprecate  should we deprecate  scheduled_task resource ?
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Atlassian logo

Erick Banks (JIRA)

unread,
Jan 17, 2018, 2:40:04 PM1/17/18
to puppe...@googlegroups.com
Erick Banks updated an issue
Investigate if we can introduce a warning when the provider has been explicitly given rather than defaulted.

Scheduled_task type and provider has been moved into its own module.

The Puppet project should introduce deprecation warnings indicating it will be removed in Puppet 6.

Erick Banks (JIRA)

unread,
Jan 25, 2018, 1:38:03 PM1/25/18
to puppe...@googlegroups.com
Erick Banks updated an issue
Investigate if we can introduce a warning when the provider  has been explicitly given  is default  rather than  defaulted  explicitly given .


Scheduled_task type and provider has been moved into its own module.

The Puppet project should introduce deprecation warnings indicating it will be removed in Puppet 6.

Josh Cooper (JIRA)

unread,
Feb 7, 2018, 2:19:02 AM2/7/18
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Fix Version/s: PUP 5.4.0
Fix Version/s: PUP 5.y
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Atlassian logo

Ethan Brown (JIRA)

unread,
Mar 5, 2018, 4:22:02 PM3/5/18
to puppe...@googlegroups.com
Ethan Brown commented on Task PUP-8349
 
Re: SPIKE scheduled_task : should we deprecate scheduled_task resource?

Josh Cooper that's fine. We're still actively discussing how we want to go about this. The scheduled_task module revives the core type and provider in the module, overriding them, and setting a new default provider, so that we can ultimately remove the old type / provider from core.

Still wondering if the best location to introduce a deprecation is in the original v1 provider in core, in the docs, in both, or in some other combination of locations.

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

Erick Banks (JIRA)

unread,
Feb 7, 2019, 8:29:14 PM2/7/19
to puppe...@googlegroups.com

Erick Banks (JIRA)

unread,
Feb 7, 2019, 8:29:20 PM2/7/19
to puppe...@googlegroups.com

Josh Cooper (JIRA)

unread,
Jul 15, 2019, 7:51:03 PM7/15/19
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages