Add link to workaround about using custom CAs in private locations #3834
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
|
This pull request does not have a backport label. Could you fix it @dedemorton? 🙏
|
mergify
bot
added
the
backport-skip
dedemorton
added
backport-8.13
mergify
bot
removed
the
backport-skip
vigneshshanmugam
previously approved these changes
Apr 29, 2024
|
Thank you @dedemorton for the help. |
Co-authored-by: Vignesh Shanmugam <[email protected]>
mergify bot
pushed a commit
that referenced
this pull request
Apr 30, 2024
…3834) * Add link to workaround about using custom CAs in private locations * Update docs/en/observability/synthetics-private-location.asciidoc Co-authored-by: Vignesh Shanmugam <[email protected]> --------- Co-authored-by: Vignesh Shanmugam <[email protected]> (cherry picked from commit 09798bb)
Merged
1 task
mergify bot
pushed a commit
that referenced
this pull request
Apr 30, 2024
…3834) * Add link to workaround about using custom CAs in private locations * Update docs/en/observability/synthetics-private-location.asciidoc Co-authored-by: Vignesh Shanmugam <[email protected]> --------- Co-authored-by: Vignesh Shanmugam <[email protected]> (cherry picked from commit 09798bb)
Merged
1 task
|
@vigneshshanmugam Before I make this change in the serverless docs, can you confirm that it is needed there? Thanks! |
|
@dedemorton Yes, it does apply to private locations in Serverless as well. |
bmorelli25
pushed a commit
that referenced
this pull request
May 1, 2024
…3834) (#3842) * Add link to workaround about using custom CAs in private locations * Update docs/en/observability/synthetics-private-location.asciidoc Co-authored-by: Vignesh Shanmugam <[email protected]> --------- Co-authored-by: Vignesh Shanmugam <[email protected]> (cherry picked from commit 09798bb) Co-authored-by: DeDe Morton <[email protected]>
bmorelli25
pushed a commit
that referenced
this pull request
May 1, 2024
…3834) (#3841) * Add link to workaround about using custom CAs in private locations * Update docs/en/observability/synthetics-private-location.asciidoc Co-authored-by: Vignesh Shanmugam <[email protected]> --------- Co-authored-by: Vignesh Shanmugam <[email protected]> (cherry picked from commit 09798bb) Co-authored-by: DeDe Morton <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3833.
Someone who is an SME should make sure this note is accurate and in the right place. Synthetics is not my area of expertise; I'm just trying to help out.
IMO pointing to that GitHub issue may not be the best approach because the details in the issue seem speculative. It would be much better if we could be proscriptive and tell users exactly how to work around the problem. That is beyond of the scope of what was requested in #3833 and would need some effort from folks outside of the docs team.
TODO (after merging):