Skip to content

Conversation

@cholick
Copy link
Contributor

@cholick cholick commented Nov 9, 2015

The template generation assumes that the cf install's consul isn't specifying the datacenter (simply using the default of dc1). This isn't true for our installation. This pull request allows the scripts to consume datacenter when present in the ingested cf manifest and defaults to dc1 when not present.

@cfdreddbot
Copy link

Hey cholick!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA.

1 similar comment
@cfdreddbot
Copy link

Hey cholick!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/107773216.

@emalm
Copy link
Contributor

emalm commented Nov 10, 2015

Thanks, @cholick! Prioritizing for review by the Diego team.

Best,
Eric, CF Runtime Diego PM

@vito vito merged commit 6b8c79b into cloudfoundry:master Nov 12, 2015
@Amit-PivotalLabs
Copy link

@vito merged commit 6 hours ago? Is he taking credit for your CI bot?

@vito
Copy link
Contributor

vito commented Nov 12, 2015

i am omnipresent

@emalm
Copy link
Contributor

emalm commented Nov 12, 2015

Yep, I thought that was weird too. Inclined to believe @vito's explanation.

kart2bc pushed a commit to kart2bc/diego-release that referenced this pull request Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants