Proposed changes

Support Cumulocity Legacy configuration upload/download operations which don't have a type property.

Since the legacy configuration operations and the new type-based file operations both use the same root fragment (c8y_UploadConfigFile and c8y_DownloadConfigFile), the only main difference is that the legacy versions don't have a type. The Cumulocity server will take responsibility of setting the c8y_ConfigurationDump inventory fragment when processing the operation status updates (see the documentation listed below).

Note: The Cumulocity legacy c8y_UploadConfigFile operation will not follow the exact legacy contract. Instead the user should use the "default" type to request the configuration from the device so that it aligns with the requesting other type-based configurations which are already supported by thin-edge.io.

Below shows an example of the operation data structure, and a reference to the Cumulocity documentation:

Legacy Config Upload Operation example

Documentation: https://cumulocity.com/docs/device-integration/fragment-library/#upload-current-legacy-configuration

Example operation body:

{
   "c8y_UploadConfigFile": {}
}

Legacy Config Download Operation

Documentation: https://cumulocity.com/docs/device-integration/fragment-library/#install-legacy-configuration

Example operation body:

{
   "c8y_DownloadConfigFile": {
       "url": "https://demos.cumulocity.com/inventory/binaries/9100",
       "c8y_ConfigurationDump": {
           "id": "9200"
       }
   }
}

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

#3284

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments