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

Possible to change KAS_BUILD_DIR within kas yaml config? #116

Open
rcross-lc opened this issue May 3, 2024 · 2 comments
Open

Possible to change KAS_BUILD_DIR within kas yaml config? #116

rcross-lc opened this issue May 3, 2024 · 2 comments

Comments

@rcross-lc
Copy link

My use case here is that I have a kirkstone.yaml and a scarthgap.yaml and I would like them to have completely separate build directories.

Is there a way to set this up so that I don't need to manage environment variables via another wrapper script?

If not, can this setting be exposed to the yaml config?

@jan-kiszka
Copy link
Collaborator

KAS_BUILD_DIR is not really a project setting, it's a local decision. Or why should all users of your configs split the build dirs like you suggest?

But even if we wanted to introduce a configurable default value to the config, that would not work across kas-container. It needs to know this value but has no parser for configs with all their includes and overrides (except for very simplistic top-level evaluations).

@rcross-lc
Copy link
Author

I think I understand the problem, I'll investigate why my scarthgap builds can't co-exist with my kirkstone builds and/or change the TMPDIR and cache directories maybe...

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

No branches or pull requests

2 participants