v1.7.0 might specify the following schemas:
Before deploying config instances to a device, the deployment’s release (
v1.7.0) is used to verify that all required config instances are present and that each instance complies with the release’s schemas.
Properties
string
A semantic version, unique for a given release.Versions must be dot-separated integers. You may optionally use a
v prefix, a prerelease suffix (e.g. -alpha.X, -beta.X, -rc.X), or a build suffix (e.g. +build-metadata).Examples: v1, 1, v2.1, 2.1, v3.2.1, 3.2.1, v4.3.2-beta.1, 4.3.2-rc.1, v5.4.3+metadata, 6.5.4-beta.2+metadata[] Config Schema
The config schemas that define compatible config instances for the release.Examples:
SCH-FmoDN, SCH-3JcLq, SCH-HHDRn[] File Rule
The file rules that are part of this release.Examples:
FLR-FmoDN, FLR-3JcLq, FLR-HHDRnView a release
To view a release and its schemas, click into the release from the releases page and switch to the Overview tab at the top.
Create a release
Releases are created via the CLI — visit the config management create a release guide. To add file rules to a release, visit the data uploads define file rules guide.Duplicate a release
Duplicating a release creates a new release with the same config schemas and git information as the original. Of course, since releases require a unique version, the duplicated release must have a different version from the original release. Duplicating a release does not duplicate the release’s deployments—only the release, its schemas, and git information are duplicated. To duplicate a release, click the ellipses (…) on the release you want to duplicate and select Duplicate.
Delete a release
Deleting a release is only possible if no deployments have been delivered to any device with that release. Otherwise, the release cannot be deleted. To delete a release, click the ellipses (…) on the release you want to delete and hit Delete.