Revisions¶
Revisions are only relevant for deployments that support the request format. Each uploaded deployment package is called a revision of a deployment version. The uploaded package will be loaded when an instance starts up. This way no changes to the environment are necessary when the deployment code changes. This speeds up the development cycle.
If your deployment package includes environment files (e.g. requirements.txt or ubiops.yaml), UbiOps will automatically build an implicit environment for you, and link it to this deployment version. However, implicit building with UbiOps is deprecated and will be removed in a future version.
After uploading a deployment package you can use the utils wait_for_.. functions to check if a deployment version, environment or revision has a successful build:
| Function | Description | Example |
|---|---|---|
| wait_for_deployment_version | Wait for successful deployment version build | ubiops.utils.wait_for_deployment_version(core_api.api_client, project_name, deployment_name, version, revision_id=response.revision) |
| wait_for_environment | Wait for successful environment build | ubiops.utils.wait_for_environment(core_api.api_client, project_name, environment_name) |
| wait_for_revision | Wait for successful revision build to be available | ubiops.utils.wait_for_environment(core_api.api_client, project_name, environment_name) |
Note: you can find the full examples of these functions here.
UbiOps maintains a full history of the ZIP packages uploaded to a version, which allows for tracing back the code that was deployed at any point in time. It is also possible to download the respective deployment package from the Revision history page in the WebApp.