luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity
open-vault/CODEOWNERS

84 lines
4.8 KiB
Plaintext
Raw Normal View History

Update CODEOWNERS
2021-10-26 15:19:23 +00:00
# Each line is a file pattern followed by one or more owners. Being an owner
# means those groups or individuals will be added as reviewers to PRs affecting
# those areas of the code.
#
Initial list for CODEOWNERS (#11682)
2021-05-24 18:14:22 +00:00
# More on CODEOWNERS files: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
Update CODEOWNERS (#13091)
2021-11-09 14:02:54 +00:00
# Select Auth engines are owned by Ecosystem
/builtin/credential/aws/ @hashicorp/vault-ecosystem
/builtin/credential/github/ @hashicorp/vault-ecosystem
/builtin/credential/ldap/ @hashicorp/vault-ecosystem
/builtin/credential/okta/ @hashicorp/vault-ecosystem
Update CODEOWNERS (#11720)
2021-05-28 03:36:46 +00:00
# Secrets engines (pki, ssh, totp and transit omitted)
/builtin/logical/aws/ @hashicorp/vault-ecosystem
/builtin/logical/cassandra/ @hashicorp/vault-ecosystem
/builtin/logical/consul/ @hashicorp/vault-ecosystem
/builtin/logical/database/ @hashicorp/vault-ecosystem
/builtin/logical/mongodb/ @hashicorp/vault-ecosystem
/builtin/logical/mssql/ @hashicorp/vault-ecosystem
/builtin/logical/mysql/ @hashicorp/vault-ecosystem
/builtin/logical/nomad/ @hashicorp/vault-ecosystem
/builtin/logical/postgresql/ @hashicorp/vault-ecosystem
/builtin/logical/rabbitmq/ @hashicorp/vault-ecosystem
Update CODEOWNERS (#12521) Ensure tech writers are aware of docs changes.
2021-09-08 22:39:07 +00:00
/plugins/ @hashicorp/vault-ecosystem
Update CODEOWNERS (#15031)
2022-04-13 22:19:21 +00:00
/vault/plugin_catalog.go @hashicorp/vault-ecosystem
Update CODEOWNERS (#12521) Ensure tech writers are aware of docs changes.
2021-09-08 22:39:07 +00:00
Replace the docs codeowner (#18790)
2023-01-23 18:02:21 +00:00
/website/content/ @yhyakuna
/website/content/docs/plugin-portal.mdx @acahn @yhyakuna
Updates codeowners for OIDC coordination with UI (#13522)
2022-01-03 19:10:22 +00:00
Update CODEOWNERS (#15095)
2022-04-19 19:45:17 +00:00
# Plugin docs
Replace the docs codeowner (#18790)
2023-01-23 18:02:21 +00:00
/website/content/docs/plugins/ @fairclothjm @yhyakuna
/website/content/docs/upgrading/plugins.mdx @fairclothjm @yhyakuna
Update CODEOWNERS (#15095)
2022-04-19 19:45:17 +00:00
Updates codeowners for OIDC coordination with UI (#13522)
2022-01-03 19:10:22 +00:00
# UI code related to Vault's JWT/OIDC auth method and OIDC provider.
Update CODEOWNERS (#15095)
2022-04-19 19:45:17 +00:00
# Changes to these files often require coordination with backend code,
# so stewards of the backend code are added below for notification.
Updates codeowners for OIDC coordination with UI (#13522)
2022-01-03 19:10:22 +00:00
/ui/app/components/auth-jwt.js @austingebauer
/ui/app/routes/vault/cluster/oidc-*.js @austingebauer
add codeowners to protect release dirs (#15711)
2022-06-06 22:06:49 +00:00
# Release config; service account is required for automation tooling.
[QT-436] Pseudo random artifact test scenarios (#18056) Introducing a new approach to testing Vault artifacts before merge and after merge/notorization/signing. Rather than run a few static scenarios across the artifacts, we now have the ability to run a pseudo random sample of scenarios across many different build artifacts. We've added 20 possible scenarios for the AMD64 and ARM64 binary bundles, which we've broken into five test groups. On any given push to a pull request branch, we will now choose a random test group and execute its corresponding scenarios against the resulting build artifacts. This gives us greater test coverage but lets us split the verification across many different pull requests. The post-merge release testing pipeline behaves in a similar fashion, however, the artifacts that we use for testing have been notarized and signed prior to testing. We've also reduce the number of groups so that we run more scenarios after merge to a release branch. We intend to take what we've learned building this in Github Actions and roll it into an easier to use feature that is native to Enos. Until then, we'll have to manually add scenarios to each matrix file and manually number the test group. It's important to note that Github requires every matrix to include at least one vector, so every artifact that is being tested must include a single scenario in order for all workflows to pass and thus satisfy branch merge requirements. * Add support for different artifact types to enos-run * Add support for different runner type to enos-run * Add arm64 scenarios to build matrix * Expand build matrices to include different variants * Update Consul versions in Enos scenarios and matrices * Refactor enos-run environment * Add minimum version filtering support to enos-run. This allows us to automatically exclude scenarios that require a more recent version of Vault * Add maximum version filtering support to enos-run. This allows us to automatically exclude scenarios that require an older version of Vault * Fix Node 12 deprecation warnings * Rename enos-verify-stable to enos-release-testing-oss * Convert artifactory matrix into enos-release-testing-oss matrices * Add all Vault editions to Enos scenario matrices * Fix verify version with complex Vault edition metadata * Rename the crt-builder to ci-helper * Add more version helpers to ci-helper and Makefile * Update CODEOWNERS for quality team * Add support for filtering matrices by group and version constraints * Add support for pseudo random test scenario execution Signed-off-by: Ryan Cragun <me@ryan.ec>
2022-12-12 20:46:04 +00:00
/.release/ @hashicorp/release-engineering @hashicorp/github-secure-vault-core @hashicorp/quality-team
/.github/workflows/build.yml @hashicorp/release-engineering @hashicorp/github-secure-vault-core @hashicorp/quality-team
# Quality engineering
/.github/ @hashicorp/quality-team
/enos/ @hashicorp/quality-team
Capture cryptosec responsibilities in CODEOWNERS (#18338) * Capture cryptosec responsibilities in CODEOWNERS * ->vault-crypto * moooore
2022-12-15 18:11:43 +00:00
# Cryptosec
Add cryptosec as codeowners to relevant docs (#19070) Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
2023-02-14 15:48:16 +00:00
/builtin/logical/pki/ @hashicorp/vault-crypto
/website/content/docs/secrets/pki/ @hashicorp/vault-crypto
/website/content/api-docs/secret/pki.mdx @hashicorp/vault-crypto
/builtin/credential/cert/ @hashicorp/vault-crypto
/website/content/docs/auth/cert.mdx @hashicorp/vault-crypto
/website/content/api-docs/auth/cert.mdx @hashicorp/vault-crypto
/builtin/logical/ssh/ @hashicorp/vault-crypto
/website/content/docs/secrets/ssh/ @hashicorp/vault-crypto
/website/content/api-docs/secret/ssh.mdx @hashicorp/vault-crypto
/builtin/logical/transit/ @hashicorp/vault-crypto
/website/content/docs/secrets/transit/ @hashicorp/vault-crypto
/website/content/api-docs/secret/transit.mdx @hashicorp/vault-crypto
/helper/random/ @hashicorp/vault-crypto
/sdk/helper/certutil/ @hashicorp/vault-crypto
/sdk/helper/cryptoutil/ @hashicorp/vault-crypto
/sdk/helper/kdf/ @hashicorp/vault-crypto
/sdk/helper/keysutil/ @hashicorp/vault-crypto
/sdk/helper/ocsp/ @hashicorp/vault-crypto
/sdk/helper/salt/ @hashicorp/vault-crypto
/sdk/helper/tlsutil/ @hashicorp/vault-crypto
/shamir/ @hashicorp/vault-crypto
/vault/barrier* @hashicorp/vault-crypto
/vault/managed_key* @hashicorp/vault-crypto
/vault/seal* @hashicorp/vault-crypto
/vault/seal/ @hashicorp/vault-crypto
/website/content/docs/configuration/seal/ @hashicorp/vault-crypto
/website/content/docs/enterprise/sealwrap.mdx @hashicorp/vault-crypto
/website/content/api-docs/system/sealwrap-rewrap.mdx @hashicorp/vault-crypto
/website/content/docs/secrets/transform/ @hashicorp/vault-crypto
/website/content/api-docs/secret/transform.mdx @hashicorp/vault-crypto
/website/content/docs/secrets/kmip-profiles.mdx @hashicorp/vault-crypto
/website/content/docs/secrets/kmip.mdx @hashicorp/vault-crypto
/website/content/api-docs/secret/kmip.mdx @hashicorp/vault-crypto
/website/content/docs/enterprise/fips/ @hashicorp/vault-crypto