Skip to content

Commit

Permalink
gen/jsonschema: regen
Browse files Browse the repository at this point in the history 
Signed-off-by: William Woodruff <[email protected]>
  • Loading branch information
@woodruffw
woodruffw committed Jul 31, 2023
1 parent 4f5b42d commit 2025521
Show file tree
Hide file tree
Showing 5 changed files with 19 additions and 19 deletions.
10 changes: 5 additions & 5 deletions gen/jsonschema/schemas/Bundle.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -71,12 +71,12 @@
},
"additionalProperties": false,
"type": "array",
"description": "This is the inclusion proof, where the timestamp is coming from the transparency log. Client verification libraries MAY provide an option to support v0.1 bundles for backwards compatibility, which may contain an inclusion promise and not an inclusion proof. In this case, the client MUST validate the promise. Verifiers SHOULD NOT allow v0.1 bundles if they're used in an ecosystem which never produced them."
"description": "An inclusion proof and an optional signed timestamp from the log. Client verification libraries MAY provide an option to support v0.1 bundles for backwards compatibility, which may contain an inclusion promise and not an inclusion proof. In this case, the client MUST validate the promise. Verifiers SHOULD NOT allow v0.1 bundles if they're used in an ecosystem which never produced them."
},
"timestamp_verification_data": {
"$ref": "#/definitions/dev.sigstore.bundle.v1.TimestampVerificationData",
"additionalProperties": false,
"description": "Timestamp verification data, over the artifact's signature."
"description": "Timestamp may also come from tlog_entries.inclusion_promise.signed_entry_timestamp."
}
},
"additionalProperties": false,
Expand Down Expand Up @@ -244,7 +244,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The index of the entry in the tree it was written to."
},
"root_hash": {
"type": "string",
Expand Down Expand Up @@ -296,7 +296,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The global index of the entry, used when querying the log by index."
},
"log_id": {
"$ref": "#/definitions/dev.sigstore.common.v1.LogId",
Expand All @@ -315,7 +315,7 @@
"inclusion_promise": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionPromise",
"additionalProperties": false,
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present."
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present. Also may be used as a signed timestamp."
},
"inclusion_proof": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionProof",
Expand Down
2 changes: 1 addition & 1 deletion gen/jsonschema/schemas/InclusionProof.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The index of the entry in the tree it was written to."
},
"root_hash": {
"type": "string",
Expand Down
10 changes: 5 additions & 5 deletions gen/jsonschema/schemas/Input.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -104,12 +104,12 @@
},
"additionalProperties": false,
"type": "array",
"description": "This is the inclusion proof, where the timestamp is coming from the transparency log. Client verification libraries MAY provide an option to support v0.1 bundles for backwards compatibility, which may contain an inclusion promise and not an inclusion proof. In this case, the client MUST validate the promise. Verifiers SHOULD NOT allow v0.1 bundles if they're used in an ecosystem which never produced them."
"description": "An inclusion proof and an optional signed timestamp from the log. Client verification libraries MAY provide an option to support v0.1 bundles for backwards compatibility, which may contain an inclusion promise and not an inclusion proof. In this case, the client MUST validate the promise. Verifiers SHOULD NOT allow v0.1 bundles if they're used in an ecosystem which never produced them."
},
"timestamp_verification_data": {
"$ref": "#/definitions/dev.sigstore.bundle.v1.TimestampVerificationData",
"additionalProperties": false,
"description": "Timestamp verification data, over the artifact's signature."
"description": "Timestamp may also come from tlog_entries.inclusion_promise.signed_entry_timestamp."
}
},
"additionalProperties": false,
Expand Down Expand Up @@ -452,7 +452,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The index of the entry in the tree it was written to."
},
"root_hash": {
"type": "string",
Expand Down Expand Up @@ -504,7 +504,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The global index of the entry, used when querying the log by index."
},
"log_id": {
"$ref": "#/definitions/dev.sigstore.common.v1.LogId",
Expand All @@ -523,7 +523,7 @@
"inclusion_promise": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionPromise",
"additionalProperties": false,
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present."
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present. Also may be used as a signed timestamp."
},
"inclusion_proof": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionProof",
Expand Down
6 changes: 3 additions & 3 deletions gen/jsonschema/schemas/TransparencyLogEntry.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The global index of the entry, used when querying the log by index."
},
"log_id": {
"$ref": "#/definitions/dev.sigstore.common.v1.LogId",
Expand All @@ -25,7 +25,7 @@
"inclusion_promise": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionPromise",
"additionalProperties": false,
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present."
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present. Also may be used as a signed timestamp."
},
"inclusion_proof": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionProof",
Expand Down Expand Up @@ -86,7 +86,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The index of the entry in the tree it was written to."
},
"root_hash": {
"type": "string",
Expand Down
10 changes: 5 additions & 5 deletions gen/jsonschema/schemas/VerificationMaterial.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,12 @@
},
"additionalProperties": false,
"type": "array",
"description": "This is the inclusion proof, where the timestamp is coming from the transparency log. Client verification libraries MAY provide an option to support v0.1 bundles for backwards compatibility, which may contain an inclusion promise and not an inclusion proof. In this case, the client MUST validate the promise. Verifiers SHOULD NOT allow v0.1 bundles if they're used in an ecosystem which never produced them."
"description": "An inclusion proof and an optional signed timestamp from the log. Client verification libraries MAY provide an option to support v0.1 bundles for backwards compatibility, which may contain an inclusion promise and not an inclusion proof. In this case, the client MUST validate the promise. Verifiers SHOULD NOT allow v0.1 bundles if they're used in an ecosystem which never produced them."
},
"timestamp_verification_data": {
"$ref": "#/definitions/dev.sigstore.bundle.v1.TimestampVerificationData",
"additionalProperties": false,
"description": "Timestamp verification data, over the artifact's signature."
"description": "Timestamp may also come from tlog_entries.inclusion_promise.signed_entry_timestamp."
}
},
"additionalProperties": false,
Expand Down Expand Up @@ -156,7 +156,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The index of the entry in the tree it was written to."
},
"root_hash": {
"type": "string",
Expand Down Expand Up @@ -208,7 +208,7 @@
"properties": {
"log_index": {
"type": "string",
"description": "The index of the entry in the log."
"description": "The global index of the entry, used when querying the log by index."
},
"log_id": {
"$ref": "#/definitions/dev.sigstore.common.v1.LogId",
Expand All @@ -227,7 +227,7 @@
"inclusion_promise": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionPromise",
"additionalProperties": false,
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present."
"description": "The inclusion promise/signed entry timestamp from the log. Required for v0.1 bundles, and MUST be verified. Optional for \u003e= v0.2 bundles, and SHOULD be verified when present. Also may be used as a signed timestamp."
},
"inclusion_proof": {
"$ref": "#/definitions/dev.sigstore.rekor.v1.InclusionProof",
Expand Down

0 comments on commit 2025521

Please sign in to comment.