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.-