Deployment updates for STAGE delete #3542
Conversation
…into yuanzhou/stage-delete
There was a problem hiding this comment.
Thanks @yuanzhou !
The remaining references to the stage environment are in legacy artillery tests. Since these are no longer in use, it is not blocking.
end-to-end/artillery/scenarios/assets.yml
end-to-end/artillery/skip-scenarios/entity-globus.yml
end-to-end/artillery/skip-scenarios/entity-provenance.yml
end-to-end/artillery/skip-scenarios/portal-details.yml
end-to-end/artillery/skip-scenarios/portal-docs.yml
end-to-end/artillery/skip-scenarios/search-ccf.yml
end-to-end/artillery/skip-scenarios/search.yml
|
@lchoy @john-conroy I couldn't test the |
In our current setup:
portal-prod.stagegoes against ALL PROD APIs and Neo4j data as well as PROD indicesportal.stagegoes against a local entity-api and search-api pointing a separate STAGE indices, but the backend data is from PRODIn the new setup:
portal-prod.testwill go against ALL PROD APIs and Neo4j data as well as PROD indicesportal.teststays the sameSo we'll have DEV/TEST/PROD eventually. The only difference is we'll no longer use STAGE environment and the separate STAGE indices.
This PR will need to go hand in hand with hubmapconsortium/gateway#318