-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Vault pg custom build #30667
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
Closed
tauhid621
wants to merge
6,868
commits into
hashicorp:release/1.9.x
from
tauhid621:vault_pg_custom_build
Closed
Vault pg custom build #30667
tauhid621
wants to merge
6,868
commits into
hashicorp:release/1.9.x
from
tauhid621:vault_pg_custom_build
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Milena Zlaticanin <[email protected]>
Co-authored-by: Amir Aslamov <[email protected]>
Co-authored-by: Paul Banks <[email protected]>
Co-authored-by: Nick Cabatoff <[email protected]>
Co-authored-by: Angel Garbarino <[email protected]>
Co-authored-by: kpcraig <[email protected]>
Co-authored-by: Angel Garbarino <[email protected]>
…crets-kv (hashicorp#29632) * Update vault-plugin-secrets-gcpkms to v0.20.0 (hashicorp#29612) * Update vault-plugin-secrets-gcpkms to v0.20.0 * Add changelog --------- Co-authored-by: hc-github-team-secure-vault-ecosystem <[email protected]> * Update vault-plugin-secrets-kv to v0.21.0 (hashicorp#29614) * Update vault-plugin-secrets-kv to v0.21.0 * Add changelog --------- Co-authored-by: hc-github-team-secure-vault-ecosystem <[email protected]> --------- Co-authored-by: hc-github-team-secure-vault-core <[email protected]> Co-authored-by: hc-github-team-secure-vault-ecosystem <[email protected]>
Co-authored-by: Jaired Jawed <[email protected]>
Co-authored-by: vinay-gopalan <[email protected]>
Co-authored-by: claire bontempo <[email protected]>
Co-authored-by: Theron Voran <[email protected]>
Co-authored-by: lane-wetmore <[email protected]>
Co-authored-by: Milena Zlaticanin <[email protected]>
Co-authored-by: Sarah Chavis <[email protected]>
Co-authored-by: Jordan Reimer <[email protected]>
… devDependencies (hashicorp#30462) * manually updated package.json and reinstalled yarn.lock * add back svg-jar * remove two types and bumpt he oidc method test waiter * Delete ui/all.txt * add back resolution for ember-cli-typescript and yarn lock remove reinstall * add oidc fixes and skip flaky test * take hds back to .1 as that was the resolution and I think it was breaking ent test on the modal. * got a little aggressive, bumping down (mostly babels) to what was resolved in yarn.lock. Note this didn't work for test waiters, I had to bump a minor to resolve a test error... * allowed one mistake ember-cli-babel
Co-authored-by: Sarah Chavis <[email protected]>
Co-authored-by: Guy J Grigsby <[email protected]>
Co-authored-by: Sarah Chavis <[email protected]>
Co-authored-by: Judith Malnick <[email protected]>
* fix json editor for firefox headless * Update json-editor-test.js * fix a11y failure that we were hitting on headless—likely a firefox vs chrome difference as it is not happing on ci * remove concurrency, not needed from backend list disable action. * attempt to stabilze mfa timeout issues * rename disable selector and refactor a flaky test
Co-authored-by: Sarah Chavis <[email protected]>
* remove e.keyCode in favor of e.key * remove key-codes.js * add changelog * update to satisfy pr comments * changes * changes Co-authored-by: Jaired Jawed <[email protected]>
Co-authored-by: kpcraig <[email protected]>
Co-authored-by: Ken Keller <[email protected]>
Co-authored-by: Luis (LT) Carbonell <[email protected]>
Co-authored-by: nphilbrook <[email protected]>
…0586) * backport: 1.19.x: Update vault-plugin-auth-cf to v0.20.1 * changelog
* Update to Go 1.24.2 (hashicorp#30272) * add changelog fix and bump go version to 1.24.3 --------- Co-authored-by: Steven Clark <[email protected]>
…30582) * no-op commit due to failed cherry-picking * Upgrade FIPS 1402 -> 1403 (hashicorp#30576) * Upgrade FIPS 1402 -> 1403 * Clean up * changelog * Revert partial test changes for skipping FIPS tests for unsupported SHA3 hashes (hashicorp#30598) --------- Co-authored-by: temp <[email protected]> Co-authored-by: Luis (LT) Carbonell <[email protected]> Co-authored-by: Steven Clark <[email protected]>
Co-authored-by: Scott Miller <[email protected]>
Co-authored-by: Steven Clark <[email protected]>
Co-authored-by: Yoko Hyakuna <[email protected]>
Co-authored-by: Yoko Hyakuna <[email protected]>
Co-authored-by: Jeremy Jeffery <[email protected]>
Co-authored-by: Ryan Cragun <[email protected]>
Co-authored-by: Ryan Cragun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is meant to generate custom build for vault
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.