Is your feature request related to a problem? Please describe.
Currently, you can't address specific revisions with Dapr. This means if you want to have a full fledge staging environment for microservices, you have to make new container app per service. It would be very handy to be able to have staging revisions,
Describe the solution you'd like.
Give the ability to override the dapr appId on revisions. It also could work differently, so that so much doesn't have to change to support this. Perhaps if it's a big change to allow for the ability to change the appid, instead, the appid for the entire container stays the same you can provide a header to specify a revision. or something to that effect.
Describe alternatives you've considered.
Theres two alternatives to fix the issue. we could hard code the revision url from our gateway. or deploy a separate container environment for staging.
We'd rather not hardcode the url, since we use dapr through out the system. And deploying a separate container environment isnt the worst solution since it does offer some separation. But it feels like the revision system loses a lot of value at that point.
duglin
commented
1 year ago
Is your feature request related to a problem? Please describe.
Currently, you can't address specific revisions with Dapr. This means if you want to have a full fledge staging environment for microservices, you have to make new container app per service. It would be very handy to be able to have staging revisions,
Describe the solution you'd like.
Give the ability to override the dapr appId on revisions. It also could work differently, so that so much doesn't have to change to support this. Perhaps if it's a big change to allow for the ability to change the appid, instead, the appid for the entire container stays the same you can provide a header to specify a revision. or something to that effect.
Describe alternatives you've considered.
Theres two alternatives to fix the issue. we could hard code the revision url from our gateway. or deploy a separate container environment for staging.
We'd rather not hardcode the url, since we use dapr through out the system. And deploying a separate container environment isnt the worst solution since it does offer some separation. But it feels like the revision system loses a lot of value at that point.