Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated documentation to clarify TLS support #9331

Closed
wants to merge 1 commit into from

Conversation

ishikhman
Copy link
Contributor

updated documentation to clarify TLS support for --remote_cache, --remote_executor and --bes_backend

Follow-up of #8061

@@ -34,6 +34,8 @@
help =
"Specifies the build event service (BES) backend endpoint as HOST or HOST:PORT. "
+ "Disabled by default."
+ "The supported schemas are grpc and grpcs (grpc with TLS enabled). "
+ "If no schema is provided bazel'll default to grpcs. Specify grpc:// schema to disable TLS."
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to imply that bes_backend should default to grpcs, but from what I've seen it doesn't.
Where's the disconnect?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is, starting from version 1.0 (it is not a part of 0.29, I can see that there was a confusion around this, sorry for that). Before 1.0, in order to get this behaviour one have to specify --incompatible_tls_enabled_removed flag.
Starting 1.0 this won't be necessary.
see #8061 for details.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ooh, I missed that! Yes, it works with Bazel 1.0 release candidate!

@irengrig irengrig added the WIP label Sep 11, 2019
@bazel-io bazel-io closed this in 9ff02a9 Sep 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants