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.

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

Create LAVA labs mapping for viewer and kcidb bridge in config file #910

Open
nuclearcat opened this issue Nov 25, 2024 · 1 comment
Open

Create LAVA labs mapping for viewer and kcidb bridge in config file #910

nuclearcat opened this issue Nov 25, 2024 · 1 comment
Labels
techdebt Something that works for now, but should be done better

Comments

@nuclearcat
Copy link
Member

#898 (review)
We must try to avoid hardcoding such values in source code.
@nuclearcat nuclearcat added the techdebt Something that works for now, but should be done better label Nov 25, 2024
@JenySadadia
Copy link
Collaborator

Yes, we need to have dynamic mapping at some point.
One way to achieve it is to read runtimes from pipeline.yaml and create a dict dynamically. All the runtimes can be fetched with configs['runtimes'] in KCIDBBridge class just like we are fetching jobs and platforms atm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
techdebt Something that works for now, but should be done better
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nuclearcat @JenySadadia