-
Notifications
You must be signed in to change notification settings - Fork 2
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
NickAkhmetov/HMP-549 Revise to use assaytype endpoint #3361
Conversation
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.
I adjusted the spacing of the commented out endpoints so they're all aligned with the USER_TEMPLATES_ENDPOINT
- this was purely an aesthetic change. The meaningful additions are the different SOFT_ASSAY_ENDPOINT
values for the TEST
, DEV
and PROD
environments and the removal of the TYPE_SERVICE
values.
This PR adjusts the generation of vitessce visualizations to be done using the
assaytype
endpoint instead of the deprecated TypeClient.The
SOFT_ASSAY_ENDPOINT
environment variable has been added to configs by Zhou. Since it is a part of the ingest-api, I've adjusted the service status table to display the ingest API URL in use by trimming the/assaytype
suffix from the soft assay endpoint.TODO:
Remove type service env variables and add assaytype endpoint env variableTroubleshoot seqfish datasets only displaying descendant pyramidsUpdate portal-visualization version