-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[appmesh] implement route retry policies #11642
Closed
2 tasks
dfezzie opened this issue
Nov 23, 2020
· 1 comment
· Fixed by #13353, linz/geostore#393, sullis/aws-cdk-java-example#66, thoughtworks/tramchester#254 or linz/elasticsearch-shipper#240
Closed
2 tasks
[appmesh] implement route retry policies #11642
dfezzie opened this issue
Nov 23, 2020
· 1 comment
· Fixed by #13353, linz/geostore#393, sullis/aws-cdk-java-example#66, thoughtworks/tramchester#254 or linz/elasticsearch-shipper#240
Labels
@aws-cdk/aws-appmesh
Related to AWS App Mesh
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
p2
Milestone
Comments
mergify bot
pushed a commit
that referenced
this issue
Mar 11, 2021
Adds route retry policies for http/http2 and gRPC routes. Closes #11642 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
This was referenced Mar 12, 2021
Merged
This was referenced Mar 17, 2021
chore(deps-dev): bump @aws-cdk/aws-lambda from 1.91.0 to 1.94.1
yglcode/cdk-stack-resource-rename#17
Closed
Closed
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-appmesh
Related to AWS App Mesh
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
p2
App Mesh supports the configuration of Retry Policies on the route objects. These should be configurable by the customer
Use Case
Customers should be able to configure the retry policies for their routes
Proposed Solution
For each route protocol, the retry policies should be configurable
Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: