Issue #7316 has been updated by Chris Price.
Putting aside the issue with the config file specifying alternate vardirs for a
moment (this is a valid issue that we need to address):
When running both master and agent/client with explicit "--confdir" and
"--vardir" options (pointing to separate directories for master vs agent), the
only errors that I get are about the face overriding puppet's "tags" and
"group" settings. I made a very small change to my cloudpack.rb file:
def add_create_options(action)
add_platform_option(action)
add_region_option(action)
add_availability_zone_option(action)
#add_tags_option(action)
add_image_option(action)
add_type_option(action)
add_keyname_option(action)
add_subnet_option(action)
#add_group_option(action)
end
To prevent those option/settings collisions, and now things work fine for me as
far as I can tell; puppet help shows the "node_aws" face as expected, and I
appear to be able to run actions inside of it (up to the point where my lack of
AWS credentials stops me).
**Of significant note here**: this means that the face is successfully loading
the cloudpack.rb file and executing the 'require' lines:
require 'rubygems'
require 'guid'
require 'fog'
require 'net/ssh'
require 'puppet/network/http_pool'
require 'puppet/cloudpack/progressbar'
require 'puppet/cloudpack/utils'
I believe that this contradicts the earlier statement about not being able to
use normal ruby "require" statements. Please correct me if I am wrong.
This still leaves open the issue about the puppet.conf file needing to be able
to specify a different vardir for both the master and the agent, which I'll
continue to investigate; but I believe that to be a much smaller problem and I
believe that the findings above may significantly narrow the scope of the
reported issue. Again, please correct me if I am mistaken.
----------------------------------------
Bug #7316: puppet face applications (subcommands) delivered via pluginsync and
as modules should work
https://projects.puppetlabs.com/issues/7316#change-65503
Author: Dan Bode
Status: Code Insufficient
Priority: Urgent
Assignee:
Category: Faces
Target version: 3.0.0
Affected Puppet version:
Keywords: face faces subcommand application module plugin pluginsync
Branch: https://github.com/puppetlabs/puppet/pull/571
If you deliver a new face that consists of:
* application
* face
* action for face
via pluginsync, then the application isn't actually found, and worse, it taunts
you by showing it to you in the list of available subcommands.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
