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

Upgrade go-control-plane / data-plane-api #240

Merged
merged 9 commits into from
Feb 15, 2018

Conversation

davecheney
Copy link
Contributor

Fixes #225

This PR finished @vaamarnath 's work in #226 in switching to the new go-control-plane release.

There are lots of changes in here due to the upstream's move from pointers to values in many places.

vaamarnath and others added 5 commits February 10, 2018 07:03
- Consumes the changes in envoyproxy/go-control-plane#39.
- Changed Gopkg.lock to pick the latest go-control-plane.
- Changed code as per the changes in the structures
  defined in go-control-plane.
- Updated the unit tests.
- Fixes issue projectcontour#225.

Signed-off-by: Amarnath <vaamarnath@gmail.com>
as it is

Signed-off-by: Amarnath <vaamarnath@gmail.com>
Signed-off-by: Dave Cheney <dave@cheney.net>
Signed-off-by: Dave Cheney <dave@cheney.net>
Incorporate the change in DiscoveryResponse.Resources moving from a
pointer to a value.

Signed-off-by: Dave Cheney <dave@cheney.net>
Internally internal/contour works with pointers to *route.VirtualHosts,
but translate them to a slice of values in the cache's Values() method.

This is a holding pattern for storing native types.Any's in caches.

Signed-off-by: Dave Cheney <dave@cheney.net>
Fix tests broken by the fact that Values() returning
[]route.VirtualHost.

Signed-off-by: Dave Cheney <dave@cheney.net>
@davecheney davecheney merged commit c4d9695 into projectcontour:master Feb 15, 2018
@davecheney davecheney deleted the fixedbugs/225 branch February 15, 2018 02:02
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.

2 participants