Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
PUP 5.4.0
-
None
-
None
-
Platform Core
-
Needs Assessment
-
Not Needed
-
release note not needed for puppet - this only affects Bolt.
-
Needs Assessment
Description
*Puppet Version: vendored
branch = feature_puppet-tasks
Describe your issue in as much detail as possible…
Describe steps to reproduce…
Desired Behavior:
*Actual Behavior:
Given the following plan
|
modules/foo/plans/init.pp |
plan foo() {
|
notice 'I am the init plan for the foo module'
|
}
|
And I use 'bolt plan show', I get the following.
[root@p0dv972ia1yz1v1 ~]# bolt plan show --modulepath ~/modules
|
(at /usr/local/share/gems/gems/bolt-9.9.afe6bdc/vendored/puppet/lib/puppet.rb:130:in `<module:Puppet>')
|
Error: The code loaded from /root/modules/foo/plans/init.pp produced plan with the wrong name, expected foo::init, actual foo on node p0dv972ia1yz1v1.delivery.puppetlabs.net
|
Failure while reading plans
|
If I attempt to run this plan it works correctly.
[root@p0dv972ia1yz1v1 ~]# bolt plan run foo --modulepath ~/modules
|
Notice: Scope(<module>/foo/plans/init.pp, 2): I am the init plan
|
There is a second related issue where both list_task and list_plan methods return objects that don't remove the init part of the task and plan names.
