Draft: feat: enable storage tier option for uploader
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
conventional commits spec?
Does this follow-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
Enable an optional storage tier when uploading datasets. The storage tier can be "HOT", or "COOL". if none was provided, Cosmosdb will use default setting for sotrage tier.
Edited by JANRAJ CJ