create a spec for service.yaml #22

rhs · 2017-07-19T17:09:20Z

No description provided.

tristanpemble · 2017-08-28T04:04:04Z

This would be helpful for future proofing service.yaml; I feel weird putting my service-specific configuration at the top level since it may collide with configuration keys added to Forge in the future. A formal spec would help

rhs · 2017-08-31T13:41:06Z

I've added a schema and you can read the docs here: https://forge.sh/reference/service-descriptor

I'm open to any ideas on avoiding collision, e.g. we could define a reserved map or something:

service.yaml:
  name: ...
  config: # guaranteed to never be used by forge
    foo: bar

rhs · 2017-09-14T17:27:34Z

I've added config to the schema as a reserved object.

rhs self-assigned this Aug 30, 2017

rhs closed this as completed Sep 14, 2017

create a spec for service.yaml #22

create a spec for service.yaml #22

rhs commented Jul 19, 2017

tristanpemble commented Aug 28, 2017

rhs commented Aug 31, 2017 •

edited

rhs commented Sep 14, 2017

create a spec for service.yaml #22

create a spec for service.yaml #22

Comments

rhs commented Jul 19, 2017

tristanpemble commented Aug 28, 2017

rhs commented Aug 31, 2017 • edited

rhs commented Sep 14, 2017

rhs commented Aug 31, 2017 •

edited