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

[RFE] Use configuration file dirname as cwd #332

Closed
rsevilla87 opened this issue May 30, 2023 · 1 comment
Closed

[RFE] Use configuration file dirname as cwd #332

rsevilla87 opened this issue May 30, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request stale Stale issue

Comments

@rsevilla87
Copy link
Member

Is your feature request related to a problem? Please describe.

When running a test, kube-burner uses the user's cwd to look for all the configuration files it needs, that's to say, if we configure an objectTemplate pointing to a file on a relative path, that path will be relative to the cwd. For example, a config file with the following objects declaration:

objects:
- objectTemplate: foo.yml

Will force to run kube-burner from the same dir where the config file is. That's not very optimal since forces the user to change of directory whenever it has to run a workload from a config file stored in a different path.

Describe the solution you'd like

It would be nice to make kube-burner to use the dirname of the configuration file as cwd, so that we can run a kube-burner workload w/o changing directory.

Potential issues

There're situation when kube-burner can dump metrics into files, where should be dump them?, in the user's cwd or in the config file dirname

This RFE is a first step to mitigate #330

@github-actions
Copy link

This issue has become stale and will be closed automatically within 7 days.

@github-actions github-actions bot added the stale Stale issue label Aug 28, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Stale issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants