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

chore(*) remove the GatewayProxyType constant #2392

Merged
merged 1 commit into from
Jul 20, 2021
Merged

chore(*) remove the GatewayProxyType constant #2392

merged 1 commit into from
Jul 20, 2021

Conversation

jpeach
Copy link
Contributor

@jpeach jpeach commented Jul 18, 2021

Summary

The GatewayProxyType constant is not actually used anywhere, and creates
some confusion with a dataplane operating in gateway mode. Delete it to
remove any ambiguity.

Full changelog

N/A

Issues resolved

N/A

Documentation

N/A

Testing

  • Unit tests
  • E2E tests
  • Manual testing on Universal
  • Manual testing on Kubernetes

Backwards compatibility

  • Add backport-to-stable label if the code is backwards compatible. Otherwise, list breaking changes.

The GatewayProxyType constant is not actually used anywhere, and creates
some confusion with a dataplane operating in gateway mode. Delete it to
remove any ambiguity.

Signed-off-by: James Peach <james.peach@konghq.com>
@jpeach jpeach requested a review from a team as a code owner July 18, 2021 22:45
@codecov-commenter
Copy link

Codecov Report

Merging #2392 (3d618d4) into master (a7c748b) will increase coverage by 0.18%.
The diff coverage is 25.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2392      +/-   ##
==========================================
+ Coverage   52.35%   52.53%   +0.18%     
==========================================
  Files         875      877       +2     
  Lines       47816    47838      +22     
==========================================
+ Hits        25033    25133     +100     
+ Misses      20747    20657      -90     
- Partials     2036     2048      +12     
Impacted Files Coverage Δ
api/mesh/v1alpha1/dataplane_helpers.go 79.32% <0.00%> (+0.84%) ⬆️
pkg/xds/sync/dataplane_watchdog.go 0.00% <0.00%> (ø)
pkg/xds/bootstrap/generator.go 63.82% <100.00%> (ø)
pkg/mads/v1/client/client.go 41.25% <0.00%> (-2.50%) ⬇️
pkg/config/app/kuma-dp/config.go 63.15% <0.00%> (-1.76%) ⬇️
api/observability/v1/mads.pb.go 34.53% <0.00%> (-1.04%) ⬇️
api/internal/util/proto/types.go 100.00% <0.00%> (ø)
api/internal/util/proto/proto.go 70.00% <0.00%> (ø)
pkg/core/resources/manager/cache.go 84.41% <0.00%> (+2.59%) ⬆️
... and 8 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7c748b...3d618d4. Read the comment docs.

@jpeach jpeach merged commit fc3614d into kumahq:master Jul 20, 2021
@jpeach jpeach deleted the chore/remove-gateway-constant branch July 20, 2021 21:24
mergify bot pushed a commit that referenced this pull request Jul 20, 2021
The GatewayProxyType constant is not actually used anywhere, and creates
some confusion with a dataplane operating in gateway mode. Delete it to
remove any ambiguity.

Signed-off-by: James Peach <james.peach@konghq.com>
(cherry picked from commit fc3614d)

# Conflicts:
#	pkg/config/app/kuma-dp/config_test.go
jpeach added a commit that referenced this pull request Jul 21, 2021
The GatewayProxyType constant is not actually used anywhere, and creates
some confusion with a dataplane operating in gateway mode. Delete it to
remove any ambiguity.

Signed-off-by: James Peach <james.peach@konghq.com>
(cherry picked from commit fc3614d)
jpeach added a commit that referenced this pull request Jul 22, 2021
The GatewayProxyType constant is not actually used anywhere, and creates
some confusion with a dataplane operating in gateway mode. Delete it to
remove any ambiguity.

Signed-off-by: James Peach <james.peach@konghq.com>
(cherry picked from commit fc3614d)

Co-authored-by: James Peach <james.peach@konghq.com>
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