bazel issue about s2a-go HOT 5 CLOSED

Thanks for reporting!
I'll update google-api-go-client to use the new release, which should fix the target naming issue.

from s2a-go.

Reporting something that may be related:

Attempting to upgrade library: https://github.com/googleapis/google-api-go-client/releases/tag/v0.118.0 in a bazel-go project with gazelle causes this error

ERROR: /home/project_name/vendor/github.com/google/s2a-go/internal/v2/tlsconfigstore/BUILD:23:11: no such package 'internal/v2/tlsconfigstore/example_cert_key': BUILD file not found in any of the following directories. Add a BUILD file to a directory to mark it as a package.
 - /home/project_name/internal/v2/tlsconfigstore/example_cert_key and referenced by '//vendor/github.com/google/s2a-go/internal/v2/tlsconfigstore:tlsconfigstore'
ERROR: Analysis of target '//apps/cell_manager/cmd:cmd' failed; build aborted: no such package 'internal/v2/tlsconfigstore/example_cert_key': BUILD file not found in any of the following directories. Add a BUILD file to a directory to mark it as a package.
 - /home/project_name/internal/v2/tlsconfigstore/example_cert_key
INFO: Elapsed time: 0.355s
I

from s2a-go.

gazelle doesn't work well with pre-existing BUILD files, especially in vendor mode.
You can delete existing BUILD files, and let gazelle regenerate them, or add a directive # gazelle:build_file_name BUILD.bazel to your project, which will tell gazelle to ignore existing BUILD files and generate BUILD.bazel files and use those instead.

from s2a-go.

v0.1.1 is working for me btw ❤️

from s2a-go.

@ankurcha created a new release v0.1.2, which should work with bazel/gazelle now

from s2a-go.