Skip to content

Commit 0b1c60b

Browse files
authored
Merge pull request #415 from cnabio/cnab-core-1.2.0-ga
Prepare for Core 1.2.0 release
2 parents 307cd58 + d2c2048 commit 0b1c60b

File tree

4 files changed

+13
-12
lines changed

4 files changed

+13
-12
lines changed

000-index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ weight: 001
55

66
# CNAB Specifications
77

8-
1. [Cloud Native Application Bundle Core 1.1.0 (CNAB1)](100-CNAB.md)
8+
1. [Cloud Native Application Bundle Core 1.2.0 (CNAB1)](100-CNAB.md)
99
- [The bundle.json File](101-bundle-json.md)
1010
- [The Invocation Image Format](102-invocation-image.md)
1111
- [The Bundle Runtime](103-bundle-runtime.md)

100-CNAB.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: CNAB Core
33
weight: 100
44
---
55

6-
# Cloud Native Application Bundle Core 1.1.0 (CNAB1)
7-
*[Final Approval, Published](901-process.md), Sept. 2019*
6+
# Cloud Native Application Bundle Core 1.2.0 (CNAB1)
7+
*[Final Approval, Published](901-process.md), May 2021*
88

99

1010
The Cloud Native Application Bundle (CNAB) is a _standard packaging format_ for multi-component distributed applications. It allows packages to target different runtimes and architectures. It empowers application distributors to package applications for deployment on a wide variety of cloud platforms, providers, and services. Furthermore, it provides necessary capabilities for delivering multi-container applications in disconnected (airgapped) environments.

101-bundle-json.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The `bundle.json` file is a representation of bundle metadata. It MUST be repres
1313
1414
A `bundle.json` is broken down into the following categories of information:
1515

16-
- The schema version of the bundle, as a string with a `v` prefix. This schema is to be referenced as `v1` or `v1.1.0`
16+
- The schema version of the bundle, as a string with a `v` prefix. This schema is to be referenced as `v1` or `v1.2.0`
1717
- The top-level package information (`name` and `version`)
1818
- `name`: The bundle name, including namespacing. The namespace can have one or more elements separated by a dot (e.g. `acme.tunnels.wordpress`). The left most element of the namespace is the most general moving toward more specific elements on the right.
1919
- `version`: Semantic version of the bundle
@@ -123,7 +123,7 @@ The following is an example of a `bundle.json` for a bundled distributed as a _t
123123
}
124124
}
125125
},
126-
"schemaVersion":"v1.1.0",
126+
"schemaVersion":"v1.2.0",
127127
"version":"0.1.2"
128128
}
129129
```
@@ -134,7 +134,7 @@ The canonical JSON version of the above is:
134134

135135
<!-- prettier-ignore -->
136136
```json
137-
{"credentials":{"hostkey":{"env":"HOST_KEY","path":"/etc/hostkey.txt"}},"custom":{"com.example.backup-preferences":{"frequency":"daily"},"com.example.duffle-bag":{"icon":"https://example.com/icon.png","iconType":"PNG"}},"definitions":{"http_port":{"default":80,"maximum":10240,"minimum":10,"type":"integer"},"port":{"maximum":65535,"minimum":1024,"type":"integer"},"string":{"type":"string"},"x509Certificate":{"contentEncoding":"base64","contentMediaType":"application/x-x509-user-cert","type":"string","writeOnly":true}},"description":"An example 'thin' helloworld Cloud-Native Application Bundle","images":{"my-microservice":{"contentDigest":"sha256:aaaaaaaaaaaa...","description":"my microservice","image":"example/microservice:1.2.3"}},"invocationImages":[{"contentDigest":"sha256:aaaaaaa...","image":"example/helloworld:0.1.0","imageType":"docker"}],"maintainers":[{"email":"[email protected]","name":"Matt Butcher","url":"https://example.com"}],"name":"helloworld","outputs":{"clientCert":{"definition":"x509Certificate","path":"/cnab/app/outputs/clientCert"},"hostName":{"applyTo":["install"],"definition":"string","description":"the hostname produced installing the bundle","path":"/cnab/app/outputs/hostname"},"port":{"definition":"port","path":"/cnab/app/outputs/port"}},"parameters":{"backend_port":{"definition":"http_port","description":"The port that the back-end will listen on","destination":{"env":"BACKEND_PORT"}}},"schemaVersion":"v1.1.0","version":"0.1.2"}
137+
{"credentials":{"hostkey":{"env":"HOST_KEY","path":"/etc/hostkey.txt"}},"custom":{"com.example.backup-preferences":{"frequency":"daily"},"com.example.duffle-bag":{"icon":"https://example.com/icon.png","iconType":"PNG"}},"definitions":{"http_port":{"default":80,"maximum":10240,"minimum":10,"type":"integer"},"port":{"maximum":65535,"minimum":1024,"type":"integer"},"string":{"type":"string"},"x509Certificate":{"contentEncoding":"base64","contentMediaType":"application/x-x509-user-cert","type":"string","writeOnly":true}},"description":"An example 'thin' helloworld Cloud-Native Application Bundle","images":{"my-microservice":{"contentDigest":"sha256:aaaaaaaaaaaa...","description":"my microservice","image":"example/microservice:1.2.3"}},"invocationImages":[{"contentDigest":"sha256:aaaaaaa...","image":"example/helloworld:0.1.0","imageType":"docker"}],"maintainers":[{"email":"[email protected]","name":"Matt Butcher","url":"https://example.com"}],"name":"helloworld","outputs":{"clientCert":{"definition":"x509Certificate","path":"/cnab/app/outputs/clientCert"},"hostName":{"applyTo":["install"],"definition":"string","description":"the hostname produced installing the bundle","path":"/cnab/app/outputs/hostname"},"port":{"definition":"port","path":"/cnab/app/outputs/port"}},"parameters":{"backend_port":{"definition":"http_port","description":"The port that the back-end will listen on","destination":{"env":"BACKEND_PORT"}}},"schemaVersion":"v1.2.0","version":"0.1.2"}
138138
```
139139

140140
What follows is an example of a thick bundle. Notice how the `invocationImage` and `images` fields reference the underlying docker image manifest (`application/vnd.docker.distribution.manifest.v2+json`), which in turn references the underlying images:
@@ -231,7 +231,7 @@ What follows is an example of a thick bundle. Notice how the `invocationImage` a
231231
}
232232
}
233233
},
234-
"schemaVersion":"v1.1.0",
234+
"schemaVersion":"v1.2.0",
235235
"version":"1.0.0"
236236
}
237237

@@ -269,7 +269,7 @@ The schema version must reference the version of the schema used for this docume
269269
- `CR` indicates that the document references a candidate recommendation. Stability is not assured.
270270
- No suffix indicates that the document references a release of the specification, and is considered stable.
271271

272-
The current schema version is `v1.1.0`, which is considered stable.
272+
The current schema version is `v1.2.0`, which is considered stable.
273273

274274
## Name and Version: Identifying Metadata
275275

@@ -940,7 +940,7 @@ A runtime MUST check that it supports any required extensions before performing
940940
"requiredExtensions":[
941941
"io.cnab.dependencies"
942942
],
943-
"schemaVersion":"v1.1.0",
943+
"schemaVersion":"v1.2.0",
944944
"version":"0.1.2"
945945
}
946946
```

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,16 @@
44

55
Cloud Native Application Bundles (CNAB) are a package format specification that describes a technology for bundling, installing, and managing distributed applications, that are by design, cloud agnostic.
66

7-
## CNAB Core 1.1.0 (Final)
7+
## CNAB Core 1.2.0 (Final)
88

9-
The CNAB Working Group with the joint approval of the Executive Directors has approved the CNAB Core 1.1.0 specification for publication. CNAB Core 1.1.0 is complete.
9+
The CNAB Working Group with the joint approval of the Executive Directors has approved the CNAB Core 1.2.0 specification for publication. CNAB Core 1.2.0 is complete.
1010

11-
For more information on the approval process, see [the process documentation](901-process.md). Further changes to CNAB Core will be considered for CNAB Core 1.2.
11+
For more information on the approval process, see [the process documentation](901-process.md). Further changes to CNAB Core will be considered for CNAB Core 1.3.
1212

1313
### Branch/Tag Structure
1414

1515
- [main](https://github.com/cnabio/cnab-spec) is the current working draft of all specs
16+
- [cnab-core-1.2.0](https://github.com/cnabio/cnab-spec/tree/cnab-core-1.2.0) is the CNAB Core 1.2.0 final draft
1617
- [cnab-core-1.1.0](https://github.com/cnabio/cnab-spec/tree/cnab-core-1.1.0) is the CNAB Core 1.1.0 final draft
1718
- [cnab-core-1.0.1](https://github.com/cnabio/cnab-spec/tree/cnab-core-1.0.1) is the CNAB Core 1.0.1 final draft
1819
- [cnab-core-1.0](https://github.com/cnabio/cnab-spec/tree/cnab-core-1.0) is the CNAB Core 1.0.0 final draft

0 commit comments

Comments
 (0)