Use remote plugins, migrate config files (grpc-ecosystem#2347)

* Upgrade buf version, use remote plugins

Removes the need to depend on protoc-gen-go
and protoc-gen-go-grpc

* Migrate to v1 of buf.gen.yaml

* Migrate buf.yaml to v1

* Update CONTRIBUTING.md references

* Regenerate files with latest buf

CONTRIBUTING.md

@@ -11,7 +11,7 @@ All submissions, including submissions by project members, require review.
 It should be as simple as this (run from the root of the repository):
 
 ```bash
-docker run -v $(pwd):/grpc-gateway -w /grpc-gateway --rm ghcr.io/grpc-ecosystem/grpc-gateway/build-env:1.16 \
+docker run -v $(pwd):/grpc-gateway -w /grpc-gateway --rm ghcr.io/grpc-ecosystem/grpc-gateway/build-env:1.17 \
     /bin/bash -c 'make install && \
         make clean && \
         make generate'
@@ -22,7 +22,7 @@ docker run -itv $(pwd):/grpc-gateway -w /grpc-gateway --entrypoint /bin/bash --r
         bazel run :buildifier'
 ```
 
-You may need to authenticate with GitHub to pull `docker.pkg.github.com/grpc-ecosystem/grpc-gateway/build-env`.
+You may need to authenticate with GitHub to pull `ghcr.io/grpc-ecosystem/grpc-gateway/build-env`.
 You can do this by following the steps on the [GitHub Package docs](https://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages#authenticating-to-github-packages).
 
 ### Using Visual Studio Code dev containers

Makefile

@@ -82,10 +82,7 @@ $(GENERATE_UNBOUND_METHODS_EXAMPLE_SRCS): $(GENERATE_UNBOUND_METHODS_EXAMPLE_SPE
 		$(EXAMPLE_CLIENT_DIR)/generateunboundmethods/git_push.sh
 
 install:
-	go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.1.0
-	go install google.golang.org/protobuf/cmd/protoc-gen-go@v1.27.1
-	go install github.com/bufbuild/buf/cmd/buf@v0.51.1
-
+	go install github.com/bufbuild/buf/cmd/buf@v1.0.0-rc2
 	go install \
 		./protoc-gen-openapiv2 \
 		./protoc-gen-grpc-gateway

README.md

@@ -123,7 +123,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    Here's an example `buf.gen.yaml` you can use to generate the stubs with [buf](https://github.com/bufbuild/buf):
 
    ```yaml
-   version: v1beta1
+   version: v1
    plugins:
      - name: go
        out: gen/go
@@ -174,7 +174,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    Here's what a `buf.gen.yaml` file might look like with this option enabled:
 
    ```yaml
-   version: v1beta1
+   version: v1
    plugins:
      - name: go
        out: gen/go
@@ -235,7 +235,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    > be added to the `deps` array in your `buf.yaml` under the name
    > `buf.build/googleapis/googleapis`:
    > ```yaml
-   > version: v1beta1
+   > version: v1
    > name: buf.build/yourorg/myprotos
    > deps:
    >   - buf.build/googleapis/googleapis
@@ -249,7 +249,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    Here's what a `buf.gen.yaml` file might look like:
 
    ```yaml
-   version: v1beta1
+   version: v1
    plugins:
      - name: go
        out: gen/go
@@ -299,7 +299,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    Here's what a `buf.gen.yaml` file might look like with this option enabled:
 
    ```yaml
-   version: v1beta1
+   version: v1
    plugins:
      - name: go
        out: gen/go
@@ -384,7 +384,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    Here's what a `buf.gen.yaml` file might look like:
 
    ```yaml
-   version: v1beta1
+   version: v1
    plugins:
      - name: go
        out: gen/go
@@ -407,7 +407,7 @@ Alternatively, see the section on remotely managed plugin versions below.
    `buf`, you can add the `buf.build/grpc-ecosystem/grpc-gateway` dependency
    to your `deps` array:
    ```yaml
-   version: v1beta1
+   version: v1
    name: buf.build/yourorg/myprotos
    deps:
      - buf.build/googleapis/googleapis
@@ -480,7 +480,7 @@ When using `buf` to generate stubs, flags and parameters are passed through
 the `opt` field in your `buf.gen.yaml` file, for example:
 
 ```yaml
-version: v1beta1
+version: v1
 plugins:
   - name: grpc-gateway
     out: gen/go

buf.gen.yaml

@@ -1,10 +1,10 @@
-version: v1beta1
+version: v1
 plugins:
-  - name: go
+  - remote: buf.build/library/plugins/go:v1.27.1-1
     out: .
     opt:
       - paths=source_relative
-  - name: go-grpc
+  - remote: buf.build/library/plugins/go-grpc:v1.1.0-2
     out: .
     opt:
       - paths=source_relative

buf.yaml

@@ -1,12 +1,13 @@
-version: v1beta1
+version: v1
 name: buf.build/grpc-ecosystem/grpc-gateway
 deps:
   - buf.build/googleapis/googleapis
 build:
-  roots:
-    - .
   excludes:
     - bazel-grpc-gateway
+breaking:
+  use:
+    - FILE
 lint:
   use:
     - DEFAULT
@@ -164,6 +165,3 @@ lint:
       - examples/internal/proto/examplepb/flow_combination.proto
       - examples/internal/proto/examplepb/openapi_merge_a.proto
       - examples/internal/proto/examplepb/openapi_merge_b.proto
-breaking:
-  use:
-    - FILE

docs/docs/tutorials/adding_annotations.md

@@ -53,7 +53,7 @@ Now that we've got the gRPC-Gateway annotations added to the proto file, we need
 We'll need to add the gRPC-Gateway generator to the generation configuration:
 
 ```yaml
-version: v1beta1
+version: v1
 plugins:
   - name: go
     out: proto
@@ -69,13 +69,10 @@ plugins:
 We'll also need to add the `googleapis` dependency to our `buf.yaml` file:
 
 ```yaml
-version: v1beta1
+version: v1
 name: buf.build/myuser/myrepo
 deps:
   - buf.build/googleapis/googleapis
-build:
-  roots:
-    - proto
 ```
 
 Then we need to run `buf mod update` to select a version of the dependency to use.

docs/docs/tutorials/generating_stubs/using_buf.md

@@ -10,24 +10,19 @@ grand_parent: Tutorials
 
 [Buf](https://github.com/bufbuild/buf) is a tool that provides various protobuf utilities such as linting, breaking change detection and generation. Please find installation instructions on [https://docs.buf.build/installation/](https://docs.buf.build/installation/).
 
-It is configured through a `buf.yaml` file that should be checked in to the root of your repository. Buf will automatically read this file if present. Configuration can also be provided via the command-line flag `--config`, which accepts a path to a `.json` or `.yaml` file, or direct JSON or YAML data.
+It is configured through a `buf.yaml` file that should be checked in to the root of your Protobuf file hierarchy. Buf will automatically read this file if present. Configuration can also be provided via the command-line flag `--config`, which accepts a path to a `.json` or `.yaml` file, or direct JSON or YAML data. As opposed to `protoc`, where all `.proto` files are manually specified on the command-line, buf operates by recursively discovering all `.proto` files under configuration and building them.
 
-All Buf operations that use your local `.proto` files as input rely on a valid build configuration. This configuration tells Buf where to search for `.proto` files, and how to handle imports. As opposed to `protoc`, where all `.proto` files are manually specified on the command-line, buf operates by recursively discovering all `.proto` files under configuration and building them.
-
-The following is an example of a valid configuration, assuming you have your `.proto` files rooted in the `proto` folder relative to the root of your repository.
+The following is an example of a valid configuration, and you would put it in the root of your Protobuf file hierarchy, e.g. in `proto/buf.yaml` relative to the root of your repository.
 
 ```yaml
-version: v1beta1
+version: v1
 name: buf.build/myuser/myrepo
-build:
-  roots:
-    - proto
 ```
 
-To generate type and gRPC stubs for Go, create the file `buf.gen.yaml` at the root of the repository:
+To generate type and gRPC stubs for Go, create the file `buf.gen.yaml`:
 
 ```yaml
-version: v1beta1
+version: v1
 plugins:
   - name: go
     out: proto