dropping unnecessary property namespacing about prometheus-boshrelease HOT 4 CLOSED

I personally like the job namespaced approach, to me it improves readability and ownership of the properties especially when a user needs to create/update/debug a deployment manifest.

OTOH, I recognize it's a pain for the release dev and might be cumbersome when using ie links. But I rather prefer to make this easier to the users than not the release developer.

from prometheus-boshrelease.

I personally like the job namespaced approach, to me it improves readability and ownership of the properties

well... i never know which property is used by which job, because there was no enforcement from bosh. we had/have jobs that were reading other jobs namespace (nats.* for example). hence we've added job level properties (http://bosh.io/docs/manifest-v2.html#instance-groups). for example:

instance_groups:
- name: prometheus
  instances: 1
  jobs:
  - name: prometheus
    properties:
      scrape_interval: something  # <-- weird if namespaced once more
      ...

In the above scenario it's crystal clear (imho) that scrape_interval belongs to prometheus job. Even better Director enforces association and doesnt not allow anyone else to access those properties. Job level properties are not merged with anything as well.

from prometheus-boshrelease.

Yes, I know job level properties, it solves some use cases, agreed, but I'm not a big fan either. Maybe I'm biased.

from prometheus-boshrelease.

Closing this. Dealing with manifest files is hard, and I said before, I feel that using the job namespaced approach is better for readability and ownership.

from prometheus-boshrelease.