d4999382a5
Currently we hardcode is_secure=False, but boto supports configuration of this option from the config file (either ~/.boto or /etc/boto.cfg) so better to do that NOTE - you will need to update your boto config to include is_secure=0 to retain current (non https) behavior, since it defaults to on ref bug 1117594 Change-Id: Ic13e8604f12d3d5be4ec132a1bc04ae7624ec85d Signed-off-by: Steven Hardy <shardy@redhat.com>
27 lines
781 B
INI
27 lines
781 B
INI
#[Credentials]
|
|
# AWS credentials, from keystone ec2-credentials-list
|
|
# Note this section should only be uncommented for per-user
|
|
# boto config files, copy this file to ~/.boto
|
|
# Alternatively the credentials can be passed into the boto
|
|
# client at constructor-time in your code
|
|
#aws_access_key_id = YOUR_KEY
|
|
#aws_secret_access_key = YOUR_SECKEY
|
|
|
|
[Boto]
|
|
# Make boto output verbose debugging information
|
|
debug = 0
|
|
|
|
# Disable https connections
|
|
is_secure = 0
|
|
|
|
# Override the default AWS endpoint to connect to heat on localhost
|
|
cfn_region_name = heat
|
|
cfn_region_endpoint = 127.0.0.1
|
|
|
|
cloudwatch_region_name = heat
|
|
cloudwatch_region_endpoint = 127.0.0.1
|
|
|
|
# Set the client retries to 1, or errors connecting to heat repeat
|
|
# which is not useful when debugging API issues
|
|
num_retries = 1
|