[Fleet] Integration update fails when changing enabled property

[aleksmaus]

Problem Description

The change in Cisco ISE 1.24.1 caused the integration upgrade failures

mapper_exception Root causes: mapper_exception the (enabled) parameter 
can't be upgraded for the object mapping [cisco_ise.log.cisco_av_pair].

The cause

The top level cisco_av_pair mapping's enabled property was changed to false.

Related information

A similar issue was reported related the to the change of subobjects property in the past that affected Okta integration:
#193044

The workaround for Okta was documented here https://support.elastic.dev/knowledge/view/1a2f83e7

Requirement

The change in the mapping's enabled property value should be handled by Fleet.

Proposed resolution

1. The mapping change was reverted for Cisco ISE integration and released with version 1.24.2
2. The breaking mapping change is planned to be applied in the next version of integration 1.25+ with constraint on 8.17 release of the stack. This requires a similar change in Kibana Fleet that was mentioned in the workaround article for Okta https://support.elastic.dev/knowledge/view/1a2f83e7

Could anyone on Kibana side prioritize this and let us know if it's feasible?

I assigned a few people to this ticket to track it. Please reassign accordingly.

Related issues

• [cisco_ise] Revert mapping change for cisco_av_pair that was introduced with 1.24.1 integrations#11800

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[kpollich]

Looks like we need another special case for rollover here 😞