fm-orchestrator

#353 [RFE] Generic key/value table for storing optional stuff
Closed Opened by fivaldi.

Closed
Reopen Issue

Inspired by PR#347.

The basic columns would be:
- id (foreign key module_builds.id)
- key
- value

The names should probably be different bacause some relational DB engines use key/value as keywords and it may behave strangely due to this.

Can you give an example of what you want to use this for?

From grooming, the aim here is to reduce the number of database upgrades we have to do.

Some observations:

  • There are only 3 buildsystems we have to support right now. We don't anticipate that growing.
  • In order to add or change a buildsystem, you have to make a code change anyways. Since you have to make a code change, adding a migration also is not that big of a deal.

We're just going to drop this. DB migrations are fine. ;)

Metadata Update from @ralph:
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/mbs/issues/353

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.