Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

HCF-329: Generate spec store with BOSH releases as directories. #50

Merged
merged 2 commits into from
Nov 6, 2015

Conversation

mook-as
Copy link
Contributor

@mook-as mook-as commented Nov 5, 2015

Requires coordination with cloudfoundry-incubator/configgin#16 - probably best to not merge until I figure out how to get a cluster built with all the changes to confirm that everything works the way I think they should.

@hcf-bot
Copy link

hcf-bot commented Nov 5, 2015

Can one of the admins verify this patch?

@@ -71,6 +73,7 @@ ip_address=`/bin/hostname -i`
--consul "${consul_address}" \
--prefix "${config_store_prefix}" \
--role "{{$role.Name}}" \
--release "" \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably shouldn't be empty? Otherwise configgin's sprintf crap will look for /spec//job/key/name and despite that maybe working it feels gross.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 646fe1b - I've heard that roles have at least one job, so grabbing the release name off the first one is probably okay. (The resulting run.sh from a unit test run looks sane.)

This assumes that roles have at least one job, and the release name of the
first job is acceptable.  This assumption should be correct for now.
@aarondl
Copy link
Contributor

aarondl commented Nov 6, 2015

LGTM

aarondl added a commit that referenced this pull request Nov 6, 2015
HCF-329: Generate spec store with BOSH releases as directories.
@aarondl aarondl merged commit 0a45219 into develop Nov 6, 2015
@aarondl aarondl deleted the marky-release-name branch November 6, 2015 00:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants