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

Backport of [VAULT-28670] Updating the consul-template. into release/1.17.x #27876

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #27799 to be assessed for backporting due to the inclusion of the label backport/1.17.x.

The below text is copied from the body of the original PR.


Description

What does this PR do?

Updates the consul-template library and it's associated dependencies.

TODO only if you're a HashiCorp employee

  • Labels: If this PR is the CE portion of an ENT change, and that ENT change is
    getting backported to N-2, use the new style backport/ent/x.x.x+ent labels
    instead of the old style backport/x.x.x labels.
  • Labels: If this PR is a CE only change, it can only be backported to N, so use
    the normal backport/x.x.x label (there should be only 1).
  • 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.

Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/jmgoldsmith/update-consult-template/mildly-new-mayfly branch from 9eaaae5 to 6cf2dcd Compare July 26, 2024 12:43
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 26, 2024
Copy link

github-actions bot commented Jul 26, 2024

Build Results:
All builds succeeded! ✅

Copy link

github-actions bot commented Jul 26, 2024

CI Results: failed ❌
Failures:

Test Type Package Test Logs
race vault/diagnose TestTLSClientCAFileCheck view test results
race vault/diagnose TestTLSIntermediateCertInClientCAFile view test results
race vault/diagnose TestTLSLeafCertInClientCAFile view test results
race vault/diagnose TestTLSMultipleRootInClietCACert view test results
race vault/diagnose TestTLSValidCert view test results
standard command TestOperatorDiagnoseCommand_Run view test results
standard command TestOperatorDiagnoseCommand_Run/validations view test results
standard command TestOperatorDiagnoseCommand_Run/validations/diagnose_listener_config_ok view test results
standard vault/diagnose TestTLSClientCAFileCheck view test results
standard vault/diagnose TestTLSIntermediateCertInClientCAFile view test results

and 13 - 10 other tests

@schavis schavis added the vault-update Used by SPE team to filter out PRs not related to content label Aug 6, 2024
@JMGoldsmith JMGoldsmith deleted the backport/jmgoldsmith/update-consult-template/mildly-new-mayfly branch December 17, 2024 15:58
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-milestone vault-update Used by SPE team to filter out PRs not related to content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants