Issue #8163 has been updated by Thomas Hallgren.
When using Cloud Pack from a web-service it is not ideal to store the configuration in the users home folder. The operating system's notion of user is whoever runs the web-service. The web-service in turn can service many users but they don't have any real accounts. We would like to provide cloud-pack based services to our users. They will all have different AWS credentials that we maintain in SimpleDB. It's easy for us to put them on disk somewhere before we call on puppet but we can't use the real home folder. Any ideas how to solve this? ---------------------------------------- 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.
