-
Notifications
You must be signed in to change notification settings - Fork 0
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
TSPS-174 renaming non cosmetic things from tsps to teaspoons #93
base: main
Are you sure you want to change the base?
Changes from all commits
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 |
---|---|---|
|
@@ -4,7 +4,7 @@ | |
|
||
## Overview | ||
|
||
Terra Scientific Pipelines Service, or teaspoons, facilitates running a number of defined scientific pipelines | ||
Terra Scientific Pipelines Service, or Teaspoons, facilitates running a number of defined scientific pipelines | ||
on behalf of users that users can't run themselves in Terra. The most common reason for this is that the pipeline | ||
accesses proprietary data that users are not allowed to access directly, but that may be used as e.g. a reference panel | ||
for imputation. | ||
|
@@ -62,7 +62,7 @@ To run locally: | |
If using Intellij (only IDE we use on the team), you can run the server with a debugger. Follow | ||
the steps above but instead of running `./gradlew bootRun` to spin up the server, you can run | ||
(debug) the App.java class through intellij and set breakpoints in the code. Be sure to set the | ||
GOOGLE_APPLICATION_CREDENTIALS=config/tsps-sa.json in the Run/Debug configuration Environment Variables. | ||
GOOGLE_APPLICATION_CREDENTIALS=config/teaspoons-sa.json in the Run/Debug configuration Environment Variables. | ||
|
||
### Running Tests/Linter Locally | ||
- Testing | ||
|
@@ -88,7 +88,7 @@ SonarQube and want to debug the problem locally, you need to get the sonar token | |
before running the gradle task. | ||
|
||
```shell | ||
export SONAR_TOKEN=$(vault read -field=sonar_token secret/secops/ci/sonarcloud/tsps) | ||
export SONAR_TOKEN=$(vault read -field=sonar_token secret/secops/ci/sonarcloud/teaspoons) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we want to change our vault path? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. good question for @choover-broad |
||
./gradlew sonarqube | ||
``` | ||
|
||
|
@@ -106,7 +106,7 @@ does all the setup for you. Clone that repo and make sure you're either on Broad | |
to the VPN. Then run the following command: | ||
|
||
```shell | ||
./db/psql-connect.sh dev tsps | ||
./db/psql-connect.sh dev teaspoons | ||
``` | ||
|
||
### Deploying to dev | ||
|
@@ -115,8 +115,8 @@ Upon merging to main, the dev environment will be automatically deployed via the | |
(that workflow is defined [here](https://github.com/DataBiosphere/terra-scientific-pipelines-service/blob/main/.github/workflows/tag-publish.yml)). | ||
|
||
The two tasks `report-to-sherlock` and `set-version-in-dev` will prompt Sherlock to deploy the new version to dev. | ||
You can check the status of the deployment in [Beehive](https://beehive.dsp-devops.broadinstitute.org/apps/tsps) and in | ||
[ArgoCD](https://ap-argocd.dsp-devops.broadinstitute.org/applications/ap-argocd/tsps-dev). | ||
You can check the status of the deployment in [Beehive](https://beehive.dsp-devops.broadinstitute.org/apps/teaspoons) and in | ||
[ArgoCD](https://ap-argocd.dsp-devops.broadinstitute.org/applications/ap-argocd/teaspoons-dev). | ||
|
||
For more information about deployment to dev, check out DevOps' [excellent documentation](https://docs.google.com/document/d/1lkUkN2KOpHKWufaqw_RIE7EN3vN4G2xMnYBU83gi8VA/). | ||
|
||
|
@@ -129,7 +129,7 @@ See [this DSP blog post](https://broadworkbench.atlassian.net/wiki/x/AoGlrg) for | |
### Running the end-to-end tests | ||
|
||
The end-to-end test is specified in `.github/workflows/run-e2e-tests.yaml`. It calls [the test script defined | ||
in the dsp-reusable-workflows repo](https://github.com/broadinstitute/dsp-reusable-workflows/blob/main/e2e-test/tsps_e2e_test.py). | ||
in the dsp-reusable-workflows repo](https://github.com/broadinstitute/dsp-reusable-workflows/blob/main/e2e-test/teaspoons_e2e_test.py). | ||
|
||
The end-to-end test is automatically run nightly on the dev environment. | ||
|
||
|
This file was deleted.
This file was deleted.
This file was deleted.
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.
how hard is it to change slack channel names?
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.
not hard!