generated from teksi/template
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Allow to load official extensions via shell #300
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
transfers all scripts to the plugin with a "_ag6496" postfix
now manually tested
Move sql to datamodel
This reverts commit 19429f7.
Values are stored directly in column so we don't have to extract them from the value list
cymed
added
datamodel
Concerns the datamodel
and removed
help wanted
Extra attention is needed
github_actions
Pull requests that update GitHub Actions code
labels
Aug 7, 2024
for more information, see https://pre-commit.ci
Merge upstream
* moving init scripts to extension folder * map update type to GUI * make scripts psycopg-suitable * activate import trigger scripts * minor fixes * remove "ON CONFLICT" * symbology trigger alterations * alter order_fct_hierarchic name * add missing semicolons * remove one comma * minor fixes * more fixes * add fk_wastewater_node to cover * bauwerkstatus import vl * jahr_umsetzung_geplant rename
Merge upstream
for more information, see https://pre-commit.ci
…stewater into ci-for-extensions
for more information, see https://pre-commit.ci
Merge upstream
Merge upstream
for more information, see https://pre-commit.ci
closing here, will be re-pushed via TEKSI 2 AG-64/96 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As suggested in https://github.com/orgs/teksi/discussions/108, we need a way to include officially supported extensions in CI and deployment of TEKSI. As a first step, this PR creates an environment from which we can install extensions. Alterations to the CI itself are not done yet.
The solution works by calling
python %tww_dir%\extensions\extension_manager.py --pg_service %myservice% --module_name tww --srid 2056 --drop-schema --extension_name demo
from the shell.In a yaml, The key informations for creation (id, directory name, schema name and variables) for the extension are defined. The code then sorts all the files in the directory defined in the yaml and executes all .sql and .py scripts in that folder
Furthermore, there are now extension flags in create_dumps.py that alter the output file name (not productive yet as we have no CD invoking all processes for extensions as well)