-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
move system view interface, grpc server, and client to stubs_oss files #29291
Conversation
CI Results:
|
Build Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This refactoring lgtm!
Looks like you were able to find a happy medium with the new ENT interface types, using the BackendConfig
, and the stubbing pattern? 🎉
@@ -0,0 +1,20 @@ | |||
// Copyright (c) HashiCorp, Inc. | |||
// SPDX-License-Identifier: MPL-2.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be BUSL-1.1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, thanks for linking the reference! Though I think I'm confused by what falls under
future releases of HashiCorp products, including HashiCorp Terraform, Vault, Consul, Boundary, Nomad, Waypoint, Packer, and Vagrant
vs.
HashiCorp APIs, SDKs, and almost all other libraries will remain MPL 2.0.
because this is a Vault SDK which seems to satisfy both to me 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
What does this PR do?
This PR refactors dynamic and extended system view interface, its gRPC server, and client to stubs_oss files. The PR prepares for the implementation for the Enterprise internal SDK
Related ENT PR: https://github.com/hashicorp/vault-enterprise/pull/7214
Ticket: VAULT-33084
RFC: https://go.hashi.co/rfc/vlt-337
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.