Hi Leandro,

I've been holding off on defaulting to the Diego backend primarily because
we planned to make that change when we shipped cf-deployment
<https://github.com/cloudfoundry/cf-deployment>. That repo is still under
development and won't be ready for a little while longer, so I think it
makes sense to go ahead and update the spiff templates in cf-release to use
Diego by default. I've written a Pivotal Tracker story that you can keep an
eye on here <https://www.pivotaltracker.com/story/show/139030003>. It
likely won't make it into CF 252, but we'll definitely have it by CF 253.

In the meantime, you can still use the `generate_deployment_manifest`
script in cf-release and use Diego; all you need to do to enable Diego is
override this property
<https://github.com/cloudfoundry/cf-release/blob/master/templates/cf.yml#L805> by
setting the value in your spiff stub. It would look something like this:

properties:
...
cc:
default_to_diego_backend: true

Feel free to reach out if you need any other help deploying.

David Sabeti
Product Manager, CF Release Integration

On Fri, Feb 3, 2017 at 1:52 AM Leandro David Cacciagioni <
leandro.21.2008(a)gmail.com> wrote:

guys is there any reason why Diego is not enabled by default in the
`generate_deployment_manifest` templates? AFAIK DEA arch is being
deprecated in a few months so I think it could be good to already have it
as default.

Then since Diego is not in the defaults which guide did I follow for AWS
diego deployment the ones in Diego docs(https://github.com/
cloudfoundry/diego-release/tree/develop/examples/aws), the ones in the
cf-release (https://github.com/cloudfoundry/cf-release/tree/
master/example_manifests) or which ones?

Thanks,
Leandro.-