equinor / flyt

Equinor Flyt (aka. VSM - Value Stream Mapping)
https://flyt.equinor.com
MIT License
4 stars 1 forks source link

Fix ServiceMessage for Flyt 2.0 #693

Closed nesadrian closed 2 months ago

nesadrian commented 4 months ago
nesadrian commented 4 months ago

@QiJin-Bouvet This is ready for test

QiJin-Bouvet commented 4 months ago
Tested with those environments below: Environment Service Message api
https://web-flyt-dev.radix.equinor.com/ https://api.statoil.com/app/mad/DEV/api/v1/ServiceMessage/Flyt
https://web-flyt-qa.radix.equinor.com/ Environment not running
https://web-flyt-test.radix.equinor.com/ https://api.statoil.com/app/mad/TEST/api/v1/ServiceMessage/Flyt
https://web-flyt-prod.radix.equinor.com/ https://api.statoil.com/app/mad/api/v1/ServiceMessage/Flyt
https://web-flyt-old.radix.equinor.com/ hardcoded

@nesadrian How about qa-graph-poc and test-graph-poc? We use them more often than the QA and TEST environment now.

QiJin-Bouvet commented 4 months ago

@nesadrian Can you make a service message in https://web-flyt-prod.radix.equinor.com/ just for testing purpose for now?

nesadrian commented 4 months ago

@QiJin-Bouvet There should already be a hardcoded servicemessage in flyt-old. POC QA and TEST are using the same endpoints as flyt-qa and flyt-test, so you can use those instead. POC QA and TEST will be removed when we have fully migrated to the new radix application anyways.

QiJin-Bouvet commented 4 months ago

https://web-flyt-prod.radix.equinor.com/ uses the same ServiceMessage endpoint as Prod flyt.equinor.com