Issue #8164 has been reported by Jeff McCune.
----------------------------------------
Bug #8164: CloudPack should have an action to write settings to a configuration
file
https://projects.puppetlabs.com/issues/8164
Author: Jeff McCune
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Keywords: cloudpack
Branch:
# Overview #
While interacting with the cloud pack actions, many mandatory CLI options are
repetitive from run to run and do not change. For example, the AMI image to
use, the platform of 'AWS', and the name of the SSH key to use.
As an end user, it would be nice to have these files stored persistently so
they do not need to be entered into the CLI each time I run cloud pack. This
is #8163
If #8163 is accepted, it would be nice to not have to edit the configuration
file by hand and instead use the CLI interface to store these settings.
For example:
puppet node config --keyname 'jeff_initial'
puppet node config --platform AWS
puppet node config --type m1.small
puppet node config --image ami-90f607f9
puppet node config --aws_access_key_id DEADBEEFCAFE
puppet node config --aws_secret_access_key somestuff/andsomeotherstuff
These configuration options would be a "one time" thing rather than required
each and every invocation of a cloud pack action as is the current state.
The end user then simply needs to execute:
puppet node create
puppet node install
puppet node ...
--
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.
