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

Allow output_directory to be configured by the configuration file or CLI argument. #569

Open
baraksalomon opened this issue Dec 23, 2024 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@baraksalomon
Copy link

baraksalomon commented Dec 23, 2024

Problem

Job outputs needs to be under a folder accessible by the UI.
If the "jobs" folder is not under root_dir the download links are not created.
I want the output folder not to be exposed in the UI but that download will still work.

Proposed solution

Allow to change the folder name from "jobs" to something like ".jobs"
This will allow the files to be accessible by links by not be displayed in the UI. (hopefully)

Additional context

I tried configuring SchedulerApp.output_directory but the logs shows:
[W 2024-12-23 09:49:44.196 SchedulerApp] Config option output_directory not recognized by SchedulerApp.

Exposing this parameter to the configuration will allow me to name it ".jobs" but its a generic solution for an existing parameter that may help others.

@baraksalomon baraksalomon added the enhancement New feature or request label Dec 23, 2024
@baraksalomon baraksalomon changed the title Expose Allow output_directory to be configured by the configuration file or CLI argument. Dec 23, 2024
@andrii-i andrii-i added this to the Future milestone Jan 7, 2025
@andrii-i
Copy link
Collaborator

andrii-i commented Jan 7, 2025

Thank you for creating this enhancement request @baraksalomon. We don't have resources to start working on this immediately but it does makes sense to implement.

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

No branches or pull requests

2 participants