You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying a release that is added to the deployment manifest via an opsfile, we get the following error: Release <release name> not defined in deployment manifest. It looks like the release (and stemcell) metadata is consumed from the provided deployment manifest (here). The metadata should be retrieved from the manifest downloaded from the bosh director because it has had the ops files applied. But the releases and stemcells still need to be uploaded before deploying.
When specifying a release that is added to the deployment manifest via an opsfile, we get the following error:
Release <release name> not defined in deployment manifest
. It looks like the release (and stemcell) metadata is consumed from the provided deployment manifest (here). The metadata should be retrieved from the manifest downloaded from the bosh director because it has had the ops files applied. But the releases and stemcells still need to be uploaded before deploying.This is a common pattern used when deploying cf-deployment, especially when adding windows cells.
Thanks,
@mdelillo @aminjam
The text was updated successfully, but these errors were encountered: