mirror of
https://github.com/hashicorp/terraform.git
synced 2026-02-03 20:50:59 -05:00
These get updated only as a side-effect of changing a go.mod file, or else our PR consistency checks would detect that and fail. The Go toolchain includes in go.sum any module it needed to retrieve to decide whether or not a module was relevant (whether there's a specific-package-based indirect dependency) and so if a particular module sees a go.sum update without an associated go.mod update then that means that the change cannot possibly affect that module's behavior at runtime.
35 lines
1.9 KiB
Text
35 lines
1.9 KiB
Text
# Each line is a file pattern followed by one or more owners.
|
|
# More on CODEOWNERS files: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
|
|
|
|
# Entries that are commented out have maintainers that are not in the
|
|
# HashiCorp organization and so cannot be automatically added as reviewers.
|
|
#
|
|
# We retain those as documentation of who agreed to maintain, but they
|
|
# cannot be used automatically by GitHub's pull request workflow and would
|
|
# make GitHub consider this file invalid if not commented.
|
|
|
|
# Remote-state backend # Maintainer
|
|
/internal/backend/remote-state/azure @hashicorp/terraform-azure
|
|
#/internal/backend/remote-state/consul Unmaintained
|
|
#/internal/backend/remote-state/cos @likexian
|
|
/internal/backend/remote-state/gcs @hashicorp/terraform-google
|
|
/internal/backend/remote-state/http @hashicorp/terraform-core
|
|
#/internal/backend/remote-state/oss @xiaozhu36
|
|
#/internal/backend/remote-state/pg @remilapeyre
|
|
/internal/backend/remote-state/s3 @hashicorp/terraform-aws
|
|
/internal/backend/remote-state/kubernetes @jrhouston @alexsomesan
|
|
|
|
# Provisioners
|
|
builtin/provisioners/file @hashicorp/terraform-core
|
|
builtin/provisioners/local-exec @hashicorp/terraform-core
|
|
builtin/provisioners/remote-exec @hashicorp/terraform-core
|
|
|
|
# go.sum files should never cause automatic review requests because they only
|
|
# ever change in response to go.mod files (our PR checks would fail if not) and
|
|
# if a specific module has _only_ a go.sum update without an associated go.mod
|
|
# update then that represents that the update cannot affect the module, and
|
|
# the Go toolchain just needed to download something new to prove that.
|
|
#
|
|
# (The last match in the file "wins", so this overrides any explicit owner
|
|
# specified above when go.sum is the only file that changed.)
|
|
*/go.sum # no owner for these
|