You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With AG-64/96 being developed, we must ask ourselves how to handle officially supported extensions in TEKSI.
For the end user it would be preferable to have a structure_with_value_lists_{supported_extension}.sql in the release assets.
For CI purposes, it would be nice to re-use the existing tests
I therefore suggest to do the following:
after initializing the empty database in docker, we loop through the setup multiple times, first the default db setup, then loading one setup per extension (adding the extensions before calling create_app.py)
add a config.py to define the translation from extension name to specific paths and variables
add a extension_manager.py in a new folder datamodel/extensions which runs the extension's scripts based on an input extension name
Alter create_dumps.py to allow dynamic names for assets
Thus, all the checks etc are re-run with every official extension. Note: I wouldn't use this for protection tubes etc, but for official extensions such as sire, agxx.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With AG-64/96 being developed, we must ask ourselves how to handle officially supported extensions in TEKSI.
I therefore suggest to do the following:
Thus, all the checks etc are re-run with every official extension. Note: I wouldn't use this for protection tubes etc, but for official extensions such as sire, agxx.
Beta Was this translation helpful? Give feedback.
All reactions