Bosh runtime config has configuration dialog without meaning about bosh-cli HOT 3 CLOSED

Dup as #7. Feel free to continue discussion there. I definitely want us to add diff functionality for both of these commands.

from bosh-cli.

i am seeing this same error.
ubuntu@pivotal-ops-manager:/tmp$ bosh -n deploy
Acting as client 'bosh_admin_client' on deployment 'prometheus' on 'p-bosh'
Getting deployment properties from director...
RSA 1024 bit CA certificates are loaded due to old openssl compatibility

Detecting deployment changes

stemcells:

• alias: trusty
  os: ubuntu-trusty
  version: '3363.29'
• alias: trusty
  os: ubuntu-trusty
  version: '3363.26'

releases:

• name: prometheus
  version: latest
• name: prometheus-custom
  version: latest

instance_groups:

• name: alertmanager
  jobs:
  • name: alertmanager
    properties:
    alertmanager:
    global:
    smtp_from: ""
    smtp_require_tls: ""
    smtp_smarthost: ""
    env:
    http_proxy: ""
    https_proxy: ""

Deploying

Director task 209373
Started preparing deployment > Preparing deployment. Failed: Runtime manifest contains the release 'prometheus' with version as 'latest'. Please specify the actual version string. (00:00:00)

Error 530001: Runtime manifest contains the release 'prometheus' with version as 'latest'. Please specify the actual version string.

Task 209373 error

For a more detailed error report, run: bosh task 209373 --debug
ubuntu@pivotal-ops-manager:/tmp$

How do i resolve this error and successfully deploy?

Thanks..

from bosh-cli.

@Murryy79, you should update your runtime config to specify an actual version for prometheus instead of using latest (e.g. 18.2.0). The director is intentionally discouraging the behavior of using latest here because it would introduce ambiguity about which version was being used at a given time (since it could refer to latest as of upload time, or latest as of last deploy time).

from bosh-cli.