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

[8.15] Add best practices for using integration assets (backport #1155) #1171

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 11, 2024

This adds a "Best practices for integrations assets" page as proposed in #248

Please see PREVIEW PAGE


This is an automatic backport of pull request #1155 done by [Mergify](https://mergify.com).

* Add restrictions for using integration assets

* fixup

* Update docs/en/ingest-management/integrations/integrations-assets-best-practices.asciidoc

Co-authored-by: Luca Belluccini <[email protected]>

---------

Co-authored-by: Luca Belluccini <[email protected]>
(cherry picked from commit d1137dd)
@mergify mergify bot requested a review from a team as a code owner July 11, 2024 19:41
@mergify mergify bot added the backport label Jul 11, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

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.

@kilfoyle kilfoyle merged commit 3f9b436 into 8.15 Jul 11, 2024
4 checks passed
@mergify mergify bot deleted the mergify/bp/8.15/pr-1155 branch July 11, 2024 20:07
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.

1 participant