This changes the dataset that the frontend code publishes markers to from microservices-demo to __all__.
Because we're sending data to an E&S team for Play V2, having the frontend be the only dataset with deploy markers is confusing and hard to understand for our script. Adding environment wide deploy markers means that no matter which dataset the user is on, they'll be able to see when the deploy happened.
We could probably update the name of the deploy to be more specific about which service is actually 'deployed' (I think it's supposed to be the 'checkout' service?)
How can we make that dataset name a bit more configurable?
Branched off of #49 -- this isn't really ready to merge to the main branch
This changes the dataset that the frontend code publishes markers to from
microservices-demo
to__all__
.Because we're sending data to an E&S team for Play V2, having the frontend be the only dataset with deploy markers is confusing and hard to understand for our script. Adding environment wide deploy markers means that no matter which dataset the user is on, they'll be able to see when the deploy happened.
Fixes # .
https://app.asana.com/0/1202400451269267/1202715843865043/f
Remaining issues / concerns:
We could probably update the name of the deploy to be more specific about which service is actually 'deployed' (I think it's supposed to be the 'checkout' service?)
How can we make that dataset name a bit more configurable?
Branched off of #49 -- this isn't really ready to merge to the main branch