Maxim Kholod
Maxim Kholod
My suggestion is to introduce a new section `cdr.*` or similar on the documents and introduce the `cdr.source.pretty_name` or smth there. This way we won't need to go through the...
During the CDR sync we had a discussion on the proposal of adding a custom section to the documents, smth like `cdr.*`. The idea didn't get traction, as it is...
@tinnytintin10 thanks for your input. I think `observer.vendor` is a very good candidate for this information! We will need to double check the use of it in the integrations, but...
@kfirpeled yes, I think it makes sense!
@JordanSh @kfirpeled, what do we mean by `Backport cloud_security_posture to current released version so it will take effect on serverless` ? As we don't have version branches, how does backporting...
To my understanding the process is the same as for any other integration and described in https://www.elastic.co/guide/en/integrations-developer/current/developer-workflow-support-old-package.html
Adding `observer.vendor` to our native integration https://github.com/elastic/integrations/pull/10945 backport PR is created https://github.com/elastic/integrations/pull/11017
New field has been added to the version 1.10.1 and the upcoming 1.11.0 version of `cloud_security_posture` integration, as well as to Wiz integration.