Open xeraa opened 2 years ago
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)
@jlind23 @ph I marked this with the control plane label as I think this goes way beyond 1 password and is a more generic problem around inputs, docs and what we recommend etc.
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
. Thank you for your contribution!
This is still a frequent discussion point
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
. Thank you for your contribution!
Maybe as a reference point: I ran roundtable discussions at ElasticON Frankfurt, Amsterdam, and NY — the lack of documentation for standalone came up in every single one...
We need to improve our documentation for the code-only configuration of integrations if we want them to be successful in (dev)ops environments. A recent Twitter discussion and multiple conversations at KubeCon Europe have shown: If it cannot be easily configured as code, it doesn't exist.
Taking the Twitter conversation as an example: I couldn't find good (or really any) documentation on how to configure our 1Password integration in standalone mode (so code-only). https://github.com/elastic/integrations/blob/main/packages/1password/manifest.yml#L32-L70 is kind of showing me what I need, but it feels more like reverse-engineering than the way we should be providing to our users.