Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

Rename Route type to HTTPRoute where applicable #1612

Merged
merged 1 commit into from
Aug 24, 2020

Conversation

shashankram
Copy link
Member

@shashankram shashankram commented Aug 24, 2020

Currently the code refers to an HTTPRoute as a Route in a traffic target
policy. Rename this to HTTPRoute to be explicit. In the future, a route
for different traffic types will be supported, ex. TCPRoute.

This also helps disambiguate the HTTP route type in the traffic target from
the XDS Route type in Envoy.

  • New Functionality [ ]
  • Documentation [ ]
  • Install [ ]
  • Control Plane [ ]
  • CLI Tool [ ]
  • Certificate Management [ ]
  • Networking [ ]
  • Metrics [ ]
  • SMI Policy [ ]
  • Security [ ]
  • Tests / CI System [ ]
  • Other [X]

Please answer the following questions with yes/no.

  • Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
    No

@shashankram shashankram added the wip Work-in-Progress label Aug 24, 2020
Currently the code refers to an HTTPRoute as a Route in a traffic target
policy. Rename this to HTTPRoute to be explicit. In the future, a route
for different traffic types will be supported, ex. TCPRoute.

Signed-off-by: Shashank Ram <shashank08@gmail.com>
@shashankram shashankram changed the title WIP: rename Rename Route type to HTTPRoute where applicable Aug 24, 2020
@shashankram shashankram removed the wip Work-in-Progress label Aug 24, 2020
@shashankram shashankram marked this pull request as ready for review August 24, 2020 22:44
@shashankram shashankram requested a review from a team as a code owner August 24, 2020 22:44
@shashankram shashankram merged commit 930991c into openservicemesh:main Aug 24, 2020
@shashankram shashankram deleted the http-route branch August 24, 2020 23:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants