octopaas versions
Freeze integrations into versions you can deploy
A version freezes an integration as it stands, definition and resources, under a tag such as v1.3.0. Deployments run versions, never the live draft, so creating one is how a change becomes deployable. The platform UI calls them snapshots.
Versions are named by tag within their integration, or by id.
Also: version-tags, ver.
Examples
octopaas versions create billing v1.3.0
octopaas versions list billingoctopaas versions create
Freeze an integration under a tag.
octopaas versions create <integration> <tag>Examples
octopaas versions create billing v1.3.0
octopaas versions create billing "$(git describe --tags)"octopaas versions list
List an integration's versions, newest first.
octopaas versions list <integration>Also: ls.
Examples
octopaas versions list billingoctopaas versions pull
Download a version, definition and frozen resources, into a folder (by default <integration>-<tag>), or with --zip as the bundle it came as.
octopaas versions pull <integration> <tag> [folder] [flags]Examples
octopaas versions pull billing v1.2.0
octopaas versions pull billing v1.2.0 --zip billing-v1.2.0.zipFlags
| Flag | What it does | Default |
|---|---|---|
--force | unpack into a folder that already has files | |
--zip | save the bundle as this .zip instead of unpacking it |
octopaas versions rm
Delete a version. A version a deployment is running cannot be deleted; undeploy or roll that deployment onto another version first.
octopaas versions rm <integration> <tag> [flags]Also: delete.
Examples
octopaas versions rm billing v1.0.0 --yesFlags
| Flag | What it does | Default |
|---|---|---|
-y, --yes | do not ask first |