Re: How to set with cf-release spiff templates ?

CF Runtime

Unfortunately those properties don't actually do what they say. A story has
been added to the CAPI backlog to clean those up, and possibly change them:

In the meantime, you can override `version` and `description`, they are
currently used to populate the info endpoint, but they may change in the
process of doing the above story.

After the story is done, we'll add the attributes to the template so they
are easy to override, but for now you'll need to manually edit your
manifest to add the `version` and `description` properties.

OSS Release Integration Team

On Thu, Aug 27, 2015 at 1:07 PM, Guillaume Berche <bercheg(a)> wrote:


I'm trying to assign and [1] (to merge
meta.releases[0].version if cf release version), as to be able to describe
to end users which cf version is currently deployed from a "cf curl
v2/info" command.

I'm however struggling with spiff syntax to do so. I trial-and-errored
around modifying cf-release/templates as to allow for the merge without
luck so far.

Anyone succeeded in doing so without forking standard spiff templates ?

Thanks in advance,



Join to automatically receive all group messages.