Skip to content
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

Disambiguate router names in example #67

Merged
merged 1 commit into from
Sep 12, 2019
Merged

Disambiguate router names in example #67

merged 1 commit into from
Sep 12, 2019

Conversation

bcelenza
Copy link
Contributor

Description of changes:

The current example template referenced in https://github.com/aws/aws-app-mesh-examples/blob/master/walkthroughs/eks/base.md has an error that results in the colorteller virtual router mapping to the color gateway's route.

This change disambiguates the routers and routes by naming the routers accordingly.

Are router names intended to be optional in the controller? If so, there is a broader bug here that warrants a separate pull request.

Testing:
Followed the guide at the walkthrough link above, observed 500 error and invalid router to route mapping in App Mesh configuration. Updated with proposed changes and mapping works as expected.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@nckturner
Copy link
Contributor

@bcelenza yes they were intended to be optional. I.e., if not specified default to service name. Can you create an issue for the broader bug?

@bcelenza
Copy link
Contributor Author

@bcelenza yes they were intended to be optional. I.e., if not specified default to service name. Can you create an issue for the broader bug?

Logged as #69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants