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

Creates Skeleton RPC to send global client data to primaries #28761

Merged
merged 3 commits into from
Oct 24, 2024

Conversation

divyaac
Copy link
Contributor

@divyaac divyaac commented Oct 24, 2024

Description

This PR creates the RPC that will send global client data from a secondary to a primary at any point that Vault is running. We will reuse the same the same RPC when Vault upgrades to 1.19 to send all of the global client data from the secondary to the primary.

To make the PR sizes manageable, this PR only creates the RPC, and sends some "dummy" data to verify that the RPC works. A following PR will be made to create functions to separate the global clients from the local clients and then send that data to the secondaries.

ENT PR: https://github.com/hashicorp/vault-enterprise/pull/6889

TODO only if you're a HashiCorp employee

  • Backport Labels: If this PR is in the ENT repo and needs to be backported, backport
    to N, N-1, and N-2, using the backport/ent/x.x.x+ent labels. If this PR is in the CE repo, you should only backport to N, using the backport/x.x.x label, not the enterprise labels.
    • If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    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.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Oct 24, 2024
@divyaac divyaac added this to the 1.19.0-rc milestone Oct 24, 2024
Copy link

github-actions bot commented Oct 24, 2024

CI Results:
All Go tests succeeded! ✅

Copy link

github-actions bot commented Oct 24, 2024

Build Results:
All builds succeeded! ✅

Copy link
Contributor

@VioletHynes VioletHynes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great :D

@@ -13,3 +13,8 @@ import (
func (a *ActivityLog) sendCurrentFragment(ctx context.Context) error {
return nil
}

// sendGlobalClients is a no-op on OSS
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: OSS -> CE

@divyaac divyaac enabled auto-merge (squash) October 24, 2024 18:34
@divyaac divyaac merged commit 5a372ee into main Oct 24, 2024
91 checks passed
@divyaac divyaac deleted the VAULT-31266_Create_RPC_To_Send_Global_Data branch October 24, 2024 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants