The links for downloading and uploading stuff are build inside DTS using env. vars. that are defined during compilation (statically). This means, that DTS has predefined during compilation links and expects cloud services to adhere to this definitions. But this is not always true, sometimes paths on the cloud do not match, or file/folder names contain chars with different case.
Examples of the issue in practice:
cannot place here internal links.
We need to define a particular way the links are generated, so the two worlds would coexist in peace.
Is there any process where the cloud services management (firmware, logs paths) is descsribed?
Question text
The links for downloading and uploading stuff are build inside DTS using env. vars. that are defined during compilation (statically). This means, that DTS has predefined during compilation links and expects cloud services to adhere to this definitions. But this is not always true, sometimes paths on the cloud do not match, or file/folder names contain chars with different case.
Examples of the issue in practice:
We need to define a particular way the links are generated, so the two worlds would coexist in peace.
Is there any process where the cloud services management (firmware, logs paths) is descsribed?