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.

Sign up for GitHub

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

Jump to bottom

Design suitable means for setting up troute configs for use inside workers, given dynamic dataset names and paths #627

Open

robertbartel opened this issue May 20, 2024 · 1 comment

Labels

bug maas

Contributor

robertbartel commented May 20, 2024

As discussed in this comment of #624:

A troute config file needs to include the path to the ngen output (and its own output). But job worker have datasets mounted in as a directory with the same name as the dataset itself. Output dataset names are based on the job id, and that is dynamically generated (at least usually).

That issue may introduce a temporary fix, but we need to ensure we have a suitable solution to this general issue.

robertbartel added bug maas labels

robertbartel mentioned this issue

Fix ngen entrypoint script for geopackage hydrofabrics #624

Merged

Contributor Author

robertbartel commented Jul 29, 2024

There is a good chance solutions for this and #407 will be related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment