Skip to content
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

Merged
merged 6 commits into from
Nov 22, 2024

Conversation

jsotobroad
Copy link
Collaborator

@jsotobroad jsotobroad commented Jun 17, 2024

Description

We decided to rename out internal short name from tsps to teaspoons. This is making the changes in our repo first so we know what downstream things we should look into changing and try to merge the changes in logical order

working workflow with the consolidated db changesets - https://bvdp-saturn-dev.appspot.com/#workspaces/teaspoons-imputation-dev/teaspoons_imputation_dev_control_workspace_20240726/job_history/89bce976-a937-4829-bbe7-ad7d4e5dece8

Jira Ticket

https://broadworkbench.atlassian.net/browse/TSPS-174

@@ -138,8 +138,8 @@ jobs:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
with:
status: failure
channel: "#terra-tsps-alerts"
username: "TSPS push to main branch"
channel: "#terra-teaspoons-alerts"
Copy link
Collaborator Author

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?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not hard!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when should we make this change? right before merging this PR?

@@ -82,7 +82,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)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to change our vault path?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good question for @choover-broad

README.md Outdated

For more information about deployment to dev, check out DevOps' [excellent documentation](https://docs.google.com/document/d/1lkUkN2KOpHKWufaqw_RIE7EN3vN4G2xMnYBU83gi8VA/).

### Tracing

We use [OpenTelemetry](https://opentelemetry.io/) for tracing, so that every request has a tracing span that can
be viewed in [Google Cloud Trace](https://cloud.google.com/trace). (This is not yet fully set up here - to be done in TSPS-107).
be viewed in [Google Cloud Trace](https://cloud.google.com/trace). (This is not yet fully set up here - to be done in Teaspoons-107).
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we change the shortname of our jira board/tickets easily and what do we rename it to if it is?

@@ -9,7 +9,7 @@ env:
pass: ${DATABASE_USER_PASSWORD:dbpwd}
user: ${DATABASE_USER:dbuser}
stairway:
name: ${STAIRWAY_DATABASE_NAME:tsps_stairway_db}
name: ${STAIRWAY_DATABASE_NAME:teaspoons_stairway_db}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

def need to make sure these database values are changed upstream

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah i wonder what the process will be for updating BEEs

@@ -138,8 +138,8 @@ jobs:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
with:
status: failure
channel: "#terra-tsps-alerts"
username: "TSPS push to main branch"
channel: "#terra-teaspoons-alerts"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not hard!

@@ -82,7 +82,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)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good question for @choover-broad

README.md Outdated

For more information about deployment to dev, check out DevOps' [excellent documentation](https://docs.google.com/document/d/1lkUkN2KOpHKWufaqw_RIE7EN3vN4G2xMnYBU83gi8VA/).

### Tracing

We use [OpenTelemetry](https://opentelemetry.io/) for tracing, so that every request has a tracing span that can
be viewed in [Google Cloud Trace](https://cloud.google.com/trace). (This is not yet fully set up here - to be done in TSPS-107).
be viewed in [Google Cloud Trace](https://cloud.google.com/trace). (This is not yet fully set up here - to be done in TEASPOONS-107).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did we decide on a new Jira handle yet?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i dont think we have. I thougth i put a comment about that somewhere but i dont see it =/

@@ -26,7 +26,7 @@
"bio.terra.common.retry.transaction",
// Stairway initialization and status
"bio.terra.common.stairway",
// Scan all TSPS service packages
// Scan all Teaspoons service packages
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we change the whole "pipelines" package to "teaspoons"? (referenced in the next line)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i actually like pipelines. Similar to like workspace manager, their package name is workspace

@@ -43,11 +43,11 @@ public MethodListResponse getAllMethods(String cbasBaseUri, String accessToken)
* .methodDescription("method description") //
* .methodSource(PostMethodRequest.MethodSourceEnum.GITHUB) // .methodUrl(pipeline.getWdlUrl()) //
* .methodVersion("1.0"); // logger.info( // "this is creating a new method in cbas: {}", //
* cbasService.createMethod( // cbasUri, samService.getTspsServiceAccountToken(),
* cbasService.createMethod( // cbasUri, samService.getTeasponnsServiceAccountToken(),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo (though I kinda love "teasponns" 😂 )

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its so hard to spell it sometimes!!!

try {
GoogleCredentials creds =
GoogleCredentials.getApplicationDefault().createScoped(SAM_OAUTH_SCOPES);
creds.refreshIfExpired();
return creds.getAccessToken().getTokenValue();
} catch (IOException e) {
throw new InternalServerErrorException(
"Internal server error retrieving TSPS credentials", e);
"Internal server error retrieving Teaspoons credentials", e);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this message get returned to the user? do we want a different user-facing name?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh thats a good point, should we say Terra Scientific Pipeline Services instead?

@@ -155,7 +155,8 @@ public <T> JobResultOrException<T> retrieveJobResult(

switch (flightState.getFlightStatus()) {
case FATAL:
logAlert("TSPS Stairway flight {} encountered dismal failure", flightState.getFlightId());
logAlert(
"Teaspoons Stairway flight {} encountered dismal failure", flightState.getFlightId());
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we probably don't need to include "teaspoons" in these log messages at all...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@@ -9,7 +9,7 @@ env:
pass: ${DATABASE_USER_PASSWORD:dbpwd}
user: ${DATABASE_USER:dbuser}
stairway:
name: ${STAIRWAY_DATABASE_NAME:tsps_stairway_db}
name: ${STAIRWAY_DATABASE_NAME:teaspoons_stairway_db}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah i wonder what the process will be for updating BEEs

@jsotobroad jsotobroad force-pushed the js_TSPS-174 branch 4 times, most recently from f675487 to e1813d1 Compare June 26, 2024 20:09
Copy link

sonarcloud bot commented Jun 26, 2024

@jsotobroad jsotobroad changed the title TSPS-174 first pass at renaming things from tsps to teaspoons TSPS-174 renaming non cosmetic things from tsps to teaspoons Jun 26, 2024
@jsotobroad jsotobroad force-pushed the js_TSPS-174 branch 2 times, most recently from 9bdcf67 to 44fcd84 Compare November 7, 2024 00:12
value: imputation
- column:
name: wdl_url
value: https://github.com/broadinstitute/warp/blob/TSPS-183_mma_beagle_imputation_hg38/pipelines/broad/arrays/imputation_beagle/ImputationBeagle.wdl
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wasnt sure if this was correct but i think this is the latest value we have

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think that's right too (it matches what we currently have)

Copy link
Collaborator

@mmorgantaylor mmorgantaylor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looking great, a couple comments/questions. is the next step to walk through this with Chelsea?

@@ -89,7 +89,7 @@ jobs:
permissions:
contents: read
id-token: write
uses: broadinstitute/dsp-reusable-workflows/.github/workflows/run_tsps_e2e_tests.yaml@main
uses: broadinstitute/dsp-reusable-workflows/.github/workflows/run_teaspoons_e2e_tests.yaml@main
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we'll need to open a PR in dsp-reusable-workflows to update the names of all the relevant files - they all say "tsps" currently, e.g. https://github.com/broadinstitute/dsp-reusable-workflows/blob/main/.github/workflows/run_tsps_e2e_tests.yaml

@@ -138,8 +138,8 @@ jobs:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
with:
status: failure
channel: "#terra-tsps-alerts"
username: "TSPS push to main branch"
channel: "#terra-teaspoons-alerts"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when should we make this change? right before merging this PR?

@@ -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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this work already? any changes we need to make in that script?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it does not, we'd have to make all the related tsps -> teaspoon changes affter this pr gets merged

README.md Outdated
@@ -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).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

current path is https://github.com/broadinstitute/dsp-reusable-workflows/blob/main/e2e-test/tsps_gcp_e2e_test.py; we should change it in that repo and here to https://github.com/broadinstitute/dsp-reusable-workflows/blob/main/e2e-test/teaspoons_gcp_e2e_test.py

<include file="changesets/20241030_add_pipeline_quotas.yaml" relativeToChangelogFile="true"/>
<include file="changesets/20241103_add_user_quotas.yaml" relativeToChangelogFile="true"/>
<include file="changesets/20241106_array_imputation_rename.yaml" relativeToChangelogFile="true"/>
<include file="changesets/20241106-base-tables.yaml" relativeToChangelogFile="true"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😍

value: imputation
- column:
name: wdl_url
value: https://github.com/broadinstitute/warp/blob/TSPS-183_mma_beagle_imputation_hg38/pipelines/broad/arrays/imputation_beagle/ImputationBeagle.wdl
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think that's right too (it matches what we currently have)

@@ -7,6 +7,7 @@

import bio.terra.pipelines.db.entities.PipelineRun;
import bio.terra.pipelines.db.repositories.PipelineRunsRepository;
import bio.terra.pipelines.db.repositories.PipelinesRepository;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was this just missing by accident before?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

huh i have no idea why that was added, i removed it and tests still seem to be passing. I prob messed up something while i was refactoring stuff 🤷

@jsotobroad
Copy link
Collaborator Author

looking great, a couple comments/questions. is the next step to walk through this with Chelsea?

yea I think the next step would be to chat with chelsea for the vault stuff and then co-ordinate the new CI with this codebase with a clean DB. For the slack and e2e test renaming stuff i figure we can knock that out as we merge this pr in

@@ -25,7 +25,7 @@ env:
authorityEndpoint: ${OIDC_AUTHORITY_ENDPOINT:https://terradevb2c.b2clogin.com/terradevb2c.onmicrosoft.com/oauth2/v2.0/authorize?p=b2c_1a_signup_signin_dev}
tokenEndpoint: ${OIDC_TOKEN_ENDPOINT:https://terradevb2c.b2clogin.com/terradevb2c.onmicrosoft.com/oauth2/v2.0/token?p=b2c_1a_signup_signin_dev}
ingress:
domainName: ${TSPS_INGRESS_DOMAIN_NAME:localhost:8080}
domainName: ${TEAPSOONS_INGRESS_DOMAIN_NAME:localhost:8080}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this env var all set up (probably a question for @choover-broad)

Copy link

sonarcloud bot commented Nov 21, 2024

@jsotobroad jsotobroad merged commit c406d89 into main Nov 22, 2024
14 checks passed
@jsotobroad jsotobroad deleted the js_TSPS-174 branch November 22, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants