feat: add Agentless Hello World integration

[nkvoll]

Proposed commit message

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[kpollich]

@jsoriano @mrodm Do you think there's a reasonable way for us to hide this integration in Kibana or will that require a code change that excludes this integration from all deployment types? Not sure if we have a flag for internal integrations like this already.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[jsoriano]

@jsoriano @mrodm Do you think there's a reasonable way for us to hide this integration in Kibana or will that require a code change that excludes this integration from all deployment types? Not sure if we have a flag for internal integrations like this already.

We don't have any way to hide integrations. While this is kept with a prerelease version at least it won't appear by default.

In any case, maybe it is not so bad to show this integration? There is an official hello-world Docker image 🙂 https://hub.docker.com/_/hello-world/

Maybe we could add a new "Sample" category, that Fleet could use to show this kind of integrations in a different way.

[jsoriano]

Maybe we could add a new "Sample" category, that Fleet could use to show this kind of integrations in a different way.

Thinking more about this I think this category can be actually useful, issue open to follow up on this elastic/package-spec#1003.

[kpollich]

Maybe we could add a new "Sample" category, that Fleet could use to show this kind of integrations in a different way.

Sure having a dedicated category for this type of package is fine with me. Perhaps the risk of having this in the UI is not so high and it'd be easy enough to just include it. If someone wants to deploy an integration that pings https://epr.elastic.co/search and logs the status code of the response then I suppose we could just let them 😁

There are lists in Kibana that allow us to exclude packages from certain deployment types, but I think these result in the packages being excluded from the Kibana APIs as well as the UIs entirely, meaning it will be slightly more difficult to install them. If the package is just available as-is in the the UI and API as "Agentless hello world" under a "Sample" category with a clear description of its intended usage then we're probably fine to just ship it.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 0c4599e

History

• 💔 Build #33080 failed ac4b894
• 💔 Build #33067 failed 8b39cac
• 💚 Build #33048 succeeded 0d69977
• 💚 Build #33044 succeeded 48a3802
• 💔 Build #33043 failed 062af80

[kpollich]

Let's not wait on elastic/package-spec#1003. We can come back and add the sample category to this package later. I vote for merging this as-is since the package is functional and in prerelease anyway. The risk of showing a "sample" package in the general integrations UI is quite low and we should just move forward here. 🚀