Update an Application

Introduction

This walkthrough describes how to update an application that already exists. If you are looking for how to upload your first application, go to Uploading application walkthrough.

Application Versioning

DCH applications follow semantic versioning and you can update an application as long as you bump the version. You cannot upload an application with a version that already exists nor upload an application with a version lower than the highest existing version of that application. The version of the application is set in the recipe file of the application. Read about how to write the recipe file here.

Operator update

If the an operator has changed, you will need to bump the operator version found in the operator manifest file. See this walkthrough for details about operators. Assuming you are using the new operator version, you will also need to update the operator version specified in the application recipe file. Since the application is using a different version of an operator, it is considered a change in the application and you will have to bump the application version as well. See "Application Versioning" above.

No operator update

If there are no changes in any operators there is no need to upload the operators again. In fact DCH will reject the upload because it will think that you are trying to upload an operator that already exists. See the Walkthrough Application: Uploading application to see how to build the archive without operators.

Upload

Use the DCH API to upload the update. You can use the DCH Swagger docs or using CURL, like the example below.

$ curl -X 'POST' \
  'https://dataclearinghouse.org/api/metis/v1/manage/application/recipes/[VENDOR_UID]' \
  -H 'accept: application/json' \
  -H 'X-Api-Key: [YOU_API_KEY]' \
  -H 'Content-Type: multipart/form-data' \
  -F 'recipeArchive=@dch_hello_world_0.0.1.tar.gz;type=application/gzip'