[PUP-8199] Parameters in Task metadata should not collide with metadata keys - Puppet Jira Server

XML

Word

Printable

Acceptance Criteria:

Hide

Tasks should be allowed to declare parameters such as description.

Show
Tasks should be allowed to declare parameters such as description .
Team:
Bolt
Sprint:
Bolt Kanban
Method Found:
Needs Assessment

Release Notes:
Bug Fix
Release Notes Summary:

Hide
This is for Bolt

This fixes a bug where bolt parameter names that conflicted with top level metadata keys(parameters, input_method etc) were ignored.

Breaking Change: Previously tasks were types in Puppet and the run task function could be called with a reference the Type itself or an instance of the type. With this change that is no longer the case and tasks must be referred to by their lower case task name
The following invocations are no longer valid
run_task(My_app::Deploy(), ....
run_task(My_app::Deploy, ....
And should be converted to
run_task(my_app::deploy, ...
or
run_task('my_app::deploy', ...

Show
This is for Bolt This fixes a bug where bolt parameter names that conflicted with top level metadata keys(parameters, input_method etc) were ignored. Breaking Change: Previously tasks were types in Puppet and the run task function could be called with a reference the Type itself or an instance of the type. With this change that is no longer the case and tasks must be referred to by their lower case task name The following invocations are no longer valid run_task(My_app::Deploy(), .... run_task(My_app::Deploy, .... And should be converted to run_task(my_app::deploy, ... or run_task('my_app::deploy', ...

If a task declares a parameter that is also a metadata key, such as description, Puppet will fail to load the task.

With BOLT-66:

$ bolt task run echo message='{"a": 1}' -n node --modulepath site

Error: attribute Echo[description] is defined as both a constant and an attribute on node mylaptop

is duplicated by

PUP-8197 Parameters property in Task metadata should be optional