Is spiff dead?


Kei YAMAZAKI
 

Hi all,

I consider use the spiff to manage a lot of manifest.
But I found statement that the spiff is not under active development.
https://github.com/cloudfoundry-incubator/spiff/commit/e7af3990e58b7390826b606d6de76ea576d9ad4f

Manifest management is very complex and cf-release has same problem ( diego-release also ).
I think the spiff is unable to resolve this problem completely and I recognize the mega team is working on this problem.

So I have questions,
- Is spiff replaced by other tool?
- How to manage manifest files in the mega team.

Thanks,


Amit Kumar Gupta
 

Spiff is not currently replaced by another tool, but it is not the ideal
tool for the job (too many features to shoot yourself in the foot with, not
enough features about BOSH knowledge, and just some general awkward hoops
it makes you jump through). We have it on our roadmap to improve manifest
generation, so we're not investing more activity into spiff that will slow
our progress towards where we eventually want to end up. For now, manifest
generation remains the same, and we will aim to introduce improvements in a
smooth manner.

A great majority of the improvements in manifest generation will come from
BOSH itself. See the bosh-notes for a list of current and upcoming
features (https://github.com/cloudfoundry/bosh-notes). Specifically the
list under the "Deployment configuration" heading in the README. Those
features open up some exciting possibilities for how simple manifest might
become.

Best,
Amit, Release Integration (MEGA) team PM

On Thu, Aug 20, 2015 at 11:29 PM, Kei YAMAZAKI <daydream.yamazaki(a)gmail.com>
wrote:

Hi all,

I consider use the spiff to manage a lot of manifest.
But I found statement that the spiff is not under active development.

https://github.com/cloudfoundry-incubator/spiff/commit/e7af3990e58b7390826b606d6de76ea576d9ad4f

Manifest management is very complex and cf-release has same problem (
diego-release also ).
I think the spiff is unable to resolve this problem completely and I
recognize the mega team is working on this problem.

So I have questions,
- Is spiff replaced by other tool?
- How to manage manifest files in the mega team.

Thanks,


Wayne E. Seguin
 

That said, you should definitely be keeping an eye on Spruce!!! ::

spruce is a domain-specific YAML merging tool, for generating BOSH
<http://bosh.io/> manifests.

It was written with the goal of being the most intuitive solution for
merging BOSH templates. As such, it pulls in a few semantics that may seem
familiar to those used to merging with the other merging tool
<https://github.com/cloudfoundry-incubator/spiff>, but there are a few key
differences.
https://github.com/geofffranks/spruce


<https://github.com/geofffranks/spruce#installation>

On Fri, Aug 21, 2015 at 12:44 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Spiff is not currently replaced by another tool, but it is not the ideal
tool for the job (too many features to shoot yourself in the foot with, not
enough features about BOSH knowledge, and just some general awkward hoops
it makes you jump through). We have it on our roadmap to improve manifest
generation, so we're not investing more activity into spiff that will slow
our progress towards where we eventually want to end up. For now, manifest
generation remains the same, and we will aim to introduce improvements in a
smooth manner.

A great majority of the improvements in manifest generation will come from
BOSH itself. See the bosh-notes for a list of current and upcoming
features (https://github.com/cloudfoundry/bosh-notes). Specifically the
list under the "Deployment configuration" heading in the README. Those
features open up some exciting possibilities for how simple manifest might
become.

Best,
Amit, Release Integration (MEGA) team PM

On Thu, Aug 20, 2015 at 11:29 PM, Kei YAMAZAKI <
daydream.yamazaki(a)gmail.com> wrote:

Hi all,

I consider use the spiff to manage a lot of manifest.
But I found statement that the spiff is not under active development.

https://github.com/cloudfoundry-incubator/spiff/commit/e7af3990e58b7390826b606d6de76ea576d9ad4f

Manifest management is very complex and cf-release has same problem (
diego-release also ).
I think the spiff is unable to resolve this problem completely and I
recognize the mega team is working on this problem.

So I have questions,
- Is spiff replaced by other tool?
- How to manage manifest files in the mega team.

Thanks,


Kei YAMAZAKI
 

Spruce looks pretty good than the other merging tool.
And it is easy to switch from the spiff.

I'll try it. Thanks!

BTW, is this tool already used in the Stark & Wayne?


Long Nguyen
 

Spruce is currently being used at Stark & Wayne. We’re still using it to work out the bugs but our goal is to replace spiff. I have used it for CF Deployments. Hopefully we can more and more community support behind it and BOSH releases can have spruce templates. :) 

Bonus: We use it to manage big concourse pipelines files by splitting it up into smaller manageable files.

On September 11, 2015 at 5:14:12 PM, Kei YAMAZAKI (daydream.yamazaki(a)gmail.com) wrote:

Spruce looks pretty good than the other merging tool.
And it is easy to switch from the spiff.

I'll try it. Thanks!

BTW, is this tool already used in the Stark & Wayne?