Release 3.6

[teresaromero]

Release 3.6 including SLO templates so its included at 9.4 stack release

Pending changes in the Spec:

• [Change Proposal] Add support for dependencies in integration packages #1083
• [Change Proposal] Add support for multiple templates in integration packages #1084
• [Change Proposal] Allow the use of otelcol inputs in integration packages #1085
• [Change Proposal] Make data stream type optional when dynamic signals are enabled #1094

Pending changes before enabling 3.6 in Kibana:

• [Fleet] Enable install esql experimental flag kibana#244655 (feature supported, but behind feature flag by now. When feature flag is disabled, related assets in packages are ignored)
• [Cloud Security] [Fleet] Add var_group components and validation kibana#249449
• [Fleet] Ensure time series index mode is not enabled on non-metrics time series for input packages kibana#251205
• [Fleet] Enable generation of OTel configuration for integration packages kibana#252949
• [Fleet] Add support for package dependencies kibana#252938
• [Fleet] Support package inputs and streams with multiple template paths kibana#252939

[jsoriano]

We are also targeting composable packages for 9.4, it'd be good to include this too in 3.6.

[jsoriano]

Conversation related to SLOs in #1062. cc @tommyers-elastic

[tommyers-elastic]

hey all, we have been doing preliminary testing with 3.6.0 and finding lots of new validation errors in existing packages. is there any migration gudie for the new required changes, or something we can use to make upgrading packages to 3.6.0 easier for folks on the integrations team?

[jsoriano]

Hey @tommyers-elastic, thanks for giving 3.6.0 a try!
What errors are you finding?
We made the constraint for agent.version mandatory, but we are going to relax this before the release (https://github.com/elastic/ingest-dev/issues/6432).
There is also a new check to prevent having duplicated tags, what produces actual issues. @teresaromero opened some PRs to fix them before 3.6 release, see elastic/integrations#16634 (comment).
Apart from that there shouldn't be many other required changes, please let us know if you find something else.

[agithomas]

There is also a new check to prevent having duplicated tags, what produces actual issues. @teresaromero opened some PRs to fix them before 3.6 release, see elastic/integrations#16634 (comment).

@jsoriano , The validation errors we are observing appear to be related to this change.

The following are the count of errors, error type observed for the nginx package

     65 SVR00006
      8 SVR00009
      4 SVR00008

The description of these error codes goes as follows

SVR00006 | Processor tag is required
SVR00008 | Pipeline on_failure must set event.kind
SVR00009 | Pipeline on_failure must set error.message

[jsoriano]

These new errors are related to https://github.com/elastic/integration-experience/issues/390 (internal).
These are recommendations that we would like to enforce at some point. By now they can be skipped through the validation.yml file.

[jsoriano]

Marked issue as blocked, and added list of issues that should be solved before releasing 3.6.0.

[seanrathier]

@teresaromero , can we remove this from the pending changes before enabling 3.6

• [Cloud-Security] Adding var-groups to support authentication vars - related to cloud connector feature integrations#16985

This is an integration depending on the package-spec 3.6

[jsoriano]

@teresaromero , can we remove this from the pending changes before enabling 3.6

* [[Cloud-Security] Adding var-groups to support authentication vars - related to cloud connector feature integrations#16985](https://github.com/elastic/integrations/pull/16985)

This is an integration depending on the package-spec 3.6

Removed, thanks!

[jsoriano]

Package Spec v3.6.0 tag pushed, but there are still some ongoing implementation PRs.