environment.yaml Parsing Picky About Spacing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
It seems the yaml parsing is very picky on the spacing. I had 3 spaces in front of "aws", and only 2 spaces in front of "canonistack." Once I added a space to canonistack it worked.
$ juju bootstrap -e canonistack
error: Environments configuration error: /home/arosales/
in "<byte string>", line 1, column 1
did not find expected key
in "<byte string>", line 12, column 3:
environments:
aws:
type: ec2
control-bucket:
admin-secret:
access-key:
secret-key:
default-series: precise
juju-origin: ppa
ssl-
authorized-
canonistack:
type: openstack_s3
control-bucket:
admin-secret:
access-key:
secret-key:
default-series: precise
juju-origin: ppa
auth-url: https:/
default-
default-
$ vi environments.yaml
--I add the correct spacing to "canonistack" and it works:--
$ juju bootstrap -e canonistack
2013-02-20 15:29:57,616 WARNING S3 API calls not using secure transport
2013-02-20 15:29:58,886 INFO Bootstrapping environment 'canonistack' (origin: ppa type: openstack_s3)...
2013-02-20 15:30:01,938 WARNING default-
2013-02-20 15:30:03,997 INFO 'bootstrap' command finished successfully
Changed in juju: | |
importance: | Undecided → Low |
status: | New → Triaged |
It would be nice for the parsing to be a little more resilient against spacing, and to provide the user with a better error message.
-thanks,
Antonio