-
Notifications
You must be signed in to change notification settings - Fork 550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
schema: Replace "bundle" with "runtime configuration" #453
Conversation
ceb4efb
to
05fbfa3
Compare
The bundle contains 'config.json' and other things, but this schema is just for 'config.json'. This is mostly: $ sed -i 's|/bundle|/runtime/config|' schema/*.json for the 'id' fields, but I also tweaked 'root.description' and the schema.json 'description'. Signed-off-by: W. Trevor King <[email protected]>
05fbfa3
to
cccd9fc
Compare
Hmm, not sure @vbatts WDYT? |
-1 We are NOT getting rid of the bundle concept at this point. |
We already discussed this on the call and agreed on keeping it. |
On Wed, May 25, 2016 at 10:54:06AM -0700, Michael Crosby wrote:
This commit was not about getting rid of the bundle concept (although To make the distinction more clear, I'll file a PR to add JSON Schema |
To make it clear that these schemas are for validating config.json (and not, for example, state JSON). I've left the IDs alone for now, because my PR adjusting those was rejected [1]. [1]: opencontainers#453 Signed-off-by: W. Trevor King <[email protected]>
To make it clear that these schemas are for validating config.json (and not, for example, state JSON). I've left the IDs alone for now, because my PR adjusting those was rejected [1]. The rule for the -schema portion is "use it for entrypoint files" [2]. [1]: opencontainers#453 [2]: opencontainers#481 (comment) Signed-off-by: W. Trevor King <[email protected]>
To make it clear that these schemas are for validating config.json (and not, for example, state JSON). I've left the IDs alone for now, because my PR adjusting those was rejected [1]. The rule for the -schema portion is "use it for entrypoint files" [2]. [1]: opencontainers#453 [2]: opencontainers#481 (comment) Signed-off-by: W. Trevor King <[email protected]>
To make it clear that these schemas are for validating config.json (and not, for example, state JSON). I've left the IDs alone for now, because my PR adjusting those was rejected [1]. The rule for the -schema portion is "use it for entrypoint files" [2]. [1]: opencontainers#453 [2]: opencontainers#481 (comment) Signed-off-by: W. Trevor King <[email protected]>
To make it clear that these schemas are for validating config.json (and not, for example, state JSON). I've left the IDs alone for now, because my PR adjusting those was rejected [1]. The rule for the -schema portion is "use it for entrypoint files" [2]. [1]: opencontainers#453 [2]: opencontainers#481 (comment) Signed-off-by: W. Trevor King <[email protected]>
The bundle contains
config.json
and other things, but this schema is just forconfig.json
. This is mostly:for the
id
fields, but I also tweakedroot.description
andconfig.json
'sdescription
.