You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a JobManagerTask is defined for a CloudJobSchedule with the key name of an EnvironmentSetting in the OutputFileBlobContainerDestination.Path, the key name is not replaced, and the path remains static. See an example below:
JobManagerTask = new JobManagerTask($"DATAMANAGER", string.Empty)
{
...
EnvironmentSettings = new List<EnvironmentSetting> {
new EnvironmentSetting("CURRENT_DATE", "$(date -u +%Y%m%d)")
},
OutputFiles = new List<OutputFile> {
new OutputFile("../*.txt",
new OutputFileDestination(new OutputFileBlobContainerDestination(
containerUrl: containerUrl,
path: $"logs/datamanager/$CURRENT_DATE")),
new OutputFileUploadOptions(OutputFileUploadCondition.TaskCompletion)
)
}
}
When executed, the logs are uploaded to: logs/datamanager/$CURRENT_DATE
Describe Preferred Solution
Support for variables defined in the EnvironmentSettings property to replace placeholders defined in OutputFileBlobContainerDestination.Path.
The text was updated successfully, but these errors were encountered:
Feature Request Description
Currently, if a JobManagerTask is defined for a CloudJobSchedule with the key name of an EnvironmentSetting in the OutputFileBlobContainerDestination.Path, the key name is not replaced, and the path remains static. See an example below:
When executed, the logs are uploaded to: logs/datamanager/$CURRENT_DATE
Describe Preferred Solution
Support for variables defined in the EnvironmentSettings property to replace placeholders defined in OutputFileBlobContainerDestination.Path.
The text was updated successfully, but these errors were encountered: