# 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.
#
# More on CODEOWNERS files: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners

# 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

# 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

/command/agent/               @hashicorp/vault-ecosystem
/plugins/                     @hashicorp/vault-ecosystem

# Disabling for now to see if manually adding the reviewer when a PR
# is ready will be more useful and accurate. There have been cases where
# docs are being reviewed against PRs that haven't been vetted for acceptance.
# /website/content/                         @taoism4504

/website/content/docs/plugin-portal.mdx   @taoism4504  @acahn

# UI code related to Vault's JWT/OIDC auth method and OIDC provider.
# Changes to these files often require coordination with backend code, 
# so stewards of the backend code are added below for notification. 
/ui/app/components/auth-jwt.js         @austingebauer
/ui/app/routes/vault/cluster/oidc-*.js @austingebauer