Please put the cloud controller job spec in the conventional location about capi-release

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/149204143

The labels on this github issue will be updated when the story is started.

[ljfranklin]

@Gerg I think this seems reasonable as it nicely groups all our bosh stuff together although the team would have to re-learn a bit of muscle memory. WDYT?

[cppforlife]

+2 for me and james m

…

Sent from my iPhone

On Aug 31, 2017, at 5:55 PM, Lyle Franklin ***@***.***> wrote: @Gerg I think this seems reasonable as it nicely groups all our bosh stuff together although the team would have to re-learn a bit of muscle memory. WDYT? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Gerg]

We discussed this as a team, and we agreed that it makes sense to move these files to their conventional locations. That said, we have other engineering priorities currently, so we will probably not work on this in the near future.

[rainmaker]

Hi Shannon,

Thanks for bringing this up. Legibility of our release is important to us, and this is a positive change in that direction. Just an FYI that we've committed these changes to develop, and they should be rolling onto master at our next release, provided that we don't see any unforeseen consequences of moving the job specs around. Hopefully it's more discoverable now.

We also realize that the shared_job_templates directory is still somewhat unconventional, since it's now stored at the top-level of the bosh release and results in symlinks being located under jobs/cloud_controller*/templates/. It seemed like much of your concern was around the location of the job spec file, so maybe this isn't as much of an issue for you. If you feel strongly about it, let us know.

Thanks for your recommendation!

Raina