Package and contact updates

AppThreat · Jan 22, 2023 · ec49355 · ec49355
1 parent c971f58
commit ec49355
Show file tree

Hide file tree

Showing 8 changed files with 434 additions and 491 deletions.
diff --git a/.github/workflows/pythonpublish.yml b/.github/workflows/pythonpublish.yml
@@ -39,9 +39,9 @@ jobs:
       - name: Release Helm package
         run: |
           cd contrib/helm/threat-db
-          echo ${{ secrets.GITHUB_TOKEN }} | helm registry login -u ${GITHUB_USERNAME} --password-stdin ghcr.io/ngcloudsec/charts
+          echo ${{ secrets.GITHUB_TOKEN }} | helm registry login -u ${GITHUB_USERNAME} --password-stdin ghcr.io/appthreat/charts
           helm package .
-          helm push threat-db-*.tgz oci://ghcr.io/ngcloudsec/charts
+          helm push threat-db-*.tgz oci://ghcr.io/appthreat/charts
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           GITHUB_USERNAME: ${{ github.actor }}

diff --git a/README.md b/README.md
@@ -5,7 +5,7 @@ ThreatDB is a graph database for application components and vulnerabilities powe
 ## Development setup
 
 ```
-git clone https://github.com/ngcloudsec/threat-db.git
+git clone https://github.com/appthreat/threat-db.git
 cd threat-db
 mkdir -p $HOME/dgraph $HOME/threatdb_data_dir
 docker compose up
@@ -18,7 +18,7 @@ This would start a threat db api server (PORT: 9000) and an instance of [dgraph]
 To create the schemas and the first administrator user.
 
 ```
-git clone https://github.com/ngcloudsec/threat-db.git
+git clone https://github.com/appthreat/threat-db.git
 pip install poetry
 poetry install
 export DGRAPH_API_KEY=changeme
@@ -35,7 +35,7 @@ mkdir -p $HOME/threatdb_data_dir
 threat_db --data-dir $HOME/threatdb_data_dir
 ```
 
-When invoked with docker compose, any .vex.json files present in the directory `THREATDB_DATA_DIR` would be imported automatically. For testing purposes, you can download some sample VEX files from [here](https://github.com/ngcloudsec/images-info/actions/workflows/build.yml)
+When invoked with docker compose, any .vex.json files present in the directory `THREATDB_DATA_DIR` would be imported automatically. For testing purposes, you can download some sample VEX files from [here](https://github.com/appthreat/images-info/actions/workflows/build.yml)
 
 ## Rest API
 

diff --git a/contrib/helm/README.md b/contrib/helm/README.md
@@ -3,5 +3,5 @@
 Install threat-db API server via helm charts
 
 ```
-helm install threat-db oci://ghcr.io/ngcloudsec/charts/threat-db --version 0.5.0
+helm install threat-db oci://ghcr.io/appthreat/charts/threat-db --version 0.5.0
 ```
diff --git a/contrib/helm/threat-db/values.yaml b/contrib/helm/threat-db/values.yaml
@@ -6,7 +6,7 @@ replicaCount: 1
 
 image: &image
   registry: ghcr.io
-  repository: ngcloudsec/threat-db
+  repository: appthreat/threat-db
   pullPolicy: Always
   # Overrides the image tag whose default is the chart appVersion.
   tag: main

diff --git a/contrib/microk8s/INSTALL.md b/contrib/microk8s/INSTALL.md
@@ -200,7 +200,7 @@ dev-db-dgraph-zero             ClusterIP   10.152.183.112   <none>        5080/T
 
 ```
 # microk8s helm uninstall threat-db-api
-microk8s helm install threat-db-api oci://ghcr.io/ngcloudsec/charts/threat-db --version 0.6.2 --set persistence.storageClass="ssd-hostpath" --set persistence.size="1Gi"
+microk8s helm install threat-db-api oci://ghcr.io/appthreat/charts/threat-db --version 0.6.2 --set persistence.storageClass="ssd-hostpath" --set persistence.size="1Gi"
 microk8s kubectl get pods
 
 microk8s kubectl logs --tail=10 threat-db-api-0