Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Environment variable support in OutputFileBlobContainerDestination.Path #130

Open
martinjoshua opened this issue May 18, 2022 · 0 comments
Labels
feature request Feature request

Comments

@martinjoshua
Copy link

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:

              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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature request
Projects
None yet
Development

No branches or pull requests

2 participants