-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Document cloud config for product intercept #227688
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
Document cloud config for product intercept #227688
Conversation
|
Pinging @elastic/appex-sharedux (Team:SharedUX) |
|
@elasticmachine merge upstream |
💚 Build Succeeded
cc @eokoneyo |
shainaraskas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these settings unique to cloud hosted? if so, might be good to add a comment below the settings for future. we're moving toward unifying the references rather than using a unique page for elastic cloud
if it's not unique to cloud hosted, then I think the settings might be missing from the general reference.
provided some copyedits as well :)
fa4d7ba to
c7a7ba4
Compare
c7a7ba4 to
d1e30bd
Compare
docs/reference/configuration-reference/product-intercept-settings.md
Outdated
Show resolved
Hide resolved
docs/reference/configuration-reference/product-intercept-settings.md
Outdated
Show resolved
Hide resolved
docs/reference/configuration-reference/product-intercept-settings.md
Outdated
Show resolved
Hide resolved
d1e30bd to
e7062f4
Compare
docs/reference/configuration-reference/product-intercept-settings.md
Outdated
Show resolved
Hide resolved
e7062f4 to
0e9d3bb
Compare
docs/reference/configuration-reference/product-intercept-settings.md
Outdated
Show resolved
Hide resolved
0e9d3bb to
c7cca49
Compare
c7cca49 to
c9f6c81
Compare
c9f6c81 to
2b67797
Compare
florent-leborgne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
Missclicked the merge after approving, hope it's ok 😅 |
## Summary Add documentation of cloud config for product intercept. Configs will be added to cloud through the following PR elastic/cloud#141517 <!--### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... -->
Summary
Add documentation of cloud config for product intercept. Configs will be added to cloud through the following PR https://github.com/elastic/cloud/pull/141517