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

[Feature] add possibility to use another name for cnf config files #1859

Closed
kosstennbl opened this issue Jan 22, 2024 · 1 comment
Closed
Labels
enhancement New feature or request

Comments

@kosstennbl
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
cnf-config option can take only files with "cnf-testsuite.yml" name, usage of other filenames causes failures or leads to very unexpected behavior.

Describe the solution you'd like
Possibility to use different names for cnf config file. Some solution would be needed for constants and "CNFManager.cnf_config_list" function. Easiest one (but not a nice one) would be allowing user to use their config name, but rename it to "cnf-testsuite.yml" on copy to internal cnfs/* directory.

Describe alternatives you've considered
Leave limitations of config naming as it is now, but give user clear error messages and don't allow him to use any other name for cnf-config parameter. Error should be given at the earliest stages so no actions would be made by the application.

**How will this be tested? aka Acceptance Criteria (optional) **

(optional: unnecessary for things like some version bumps etc.)

Once this issue is addressed how will the fix be verified?

@kosstennbl
Copy link
Collaborator Author

Duplicate of #1429
Should be further discussed there.

@kosstennbl kosstennbl closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
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

1 participant