-
Notifications
You must be signed in to change notification settings - Fork 8
chore: remove data load #43
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
base: develop
Are you sure you want to change the base?
Changes from all commits
4adff56
3a98ee4
8ca0113
a1b964f
0c471d9
ff78329
0139860
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,9 +19,9 @@ jobs: | |
| password: ${{ secrets.GITHUB_TOKEN }} | ||
| - name: Build the pgsql EMPTY Docker image | ||
| run: | | ||
| docker build . --target base --tag ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }}-base | ||
| docker push ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }}-base | ||
| docker build . --target base --tag ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }} | ||
| docker push ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }} | ||
| - name: Build the pgsql DEMO Docker image | ||
| run: | | ||
| docker build . --tag ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }} | ||
| docker push ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }} | ||
| docker build . --tag ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }}-demo | ||
| docker push ghcr.io/openimis/openimis-pgsql:${{ github.event.inputs.tag }}-demo | ||
|
Comment on lines
+22
to
+27
|
||
Large diffs are not rendered by default.
This file was deleted.
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similarly for the
developchannel, thedeveloptag now publishes the base/empty image, which can break environments that trackdevelopand expect the demo dataset. If this is intentional, it should be paired with an explicit migration path (e.g., keep pushingdevelopdemo as well, or update any deployment manifests/README references that pulldevelop).