https://github.com/tkobayas/drools-cloudevents-operator/blob/configurable-rules/README_configurable-rules.md

There are dark mode theme guide for PatternFly and a guide on how to create one that can be used to achieve this.

https://www.patternfly.org/developer-resources/dark-theme-handbook/

The setup for DB entities is pretty easy. Getting this to work on a demo level should be fast and easy.

One example for this. https://quarkus.io/guides/hibernate-orm

Currently the path to the Akrivis quarkus runtime is hard coded in the backstage codes. Should come from configuration.

On an actual database (set up with docker compose)

Currently the file inherits everything from top down and one conf file is used for each scorecard in the same folder.

The idea I had is that the closer the configuration is, the higher override value it has. So the one in the same folder overrides the content from the parent folder and a file can have a dedicated configuration file. If the file name is myscorecard.yml having myscorecard.configuration.yml would be closer for that file than the file defined in the folder.

The configuration should also allow setting Tresholds and having one or more data sources for use. Something like below.

maxValue: 100
tresholds:
  - name: Looks ok
    value: 50
  - name: Almost there
    value: 80
  - name: Good to go
    value: 100
sources: 
  - from: http://localhost:8081/jira/example1
    outputs:
      - name: Number of Jira Issues
        from: total```