Issue #8163 has been updated by Nigel Kersten.

Thomas, ultimately we want to move to a point where puppet masters can provide 
this as a service, so you can store AWS credentials in a central location for 
enterprise management, and then specify who can use that service, rather than 
copying credentials all over the place.

It sounds like it might be worth collaborating with you on this sooner rather 
than later then :)
----------------------------------------
Feature #8163: CloudPack should have one configuration file
https://projects.puppetlabs.com/issues/8163

Author: Jeff McCune
Status: Accepted
Priority: Normal
Assignee: 
Category: cloudpack
Target version: 
Keywords: cloudpack
Branch: 
Roadmapped: No


# Overview #

Related to #8162, cloud pack currently draws settings from two locations:

 * `~/.fog`
 * command line "options"

In order to provide a better experience and more "puppet specific" I think all 
configuration settings should be placed into a file named `~/.cloudpack` or 
something similar.

This feature will serve two purposes:

 * Allow options to be optional
 * Provide better branding by hiding the Fog implementation details

# Recommendation #

A simple YAML file merged with the options hash already present in the Faces 
API could be an MVP for this ticket.



-- 
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.

Reply via email to