[Actions] Migrate cases configuration object

[cnasikas]

Summary

#73778, #74357, and #68464 renamed the cases configuration object from casesConfiguration to incidentConfiguration. This PR creates a migration to accommodate this change.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[gmmorris]

I'd suggest adding an end-to-end test for this, as I think you might find that this update results in a partial update which means you'll end up with the incidentConfiguration long side casesConfiguration instead of replacing it. 🤔

I can't recall if the migration uses update under the hood or not...

If so, you'll need to reset casesConfiguration by setting it to null or something like that

Here's an example of how this can be achieved: https://github.com/elastic/kibana/blob/master/x-pack/test/alerting_api_integration/spaces_only/tests/alerting/migrations.ts

[YulNaumenko]

Code LGTM. I agree with Gidi, that it would be very useful to have end-to-end test for like he proposed. So, please add a functional test and don't hesitate to contact me if you need any help on this.

[cnasikas]

I'd suggest adding an end-to-end test for this, as I think you might find that this update results in a partial update which means you'll end up with the incidentConfiguration long side casesConfiguration instead of replacing it. 🤔

I can't recall if the migration uses update under the hood or not...

If so, you'll need to reset casesConfiguration by setting it to null or something like that

Here's an example of how this can be achieved: https://github.com/elastic/kibana/blob/master/x-pack/test/alerting_api_integration/spaces_only/tests/alerting/migrations.ts

Thanks a lot! I will add an end-to-end test for this. Migrations do not update the SO. They create a new index, read your SO from the old index, transform it as your likes, and then the new SO will be added to the new index. Its more like a delete and create operation than an update.

Code LGTM. I agree with Gidi, that it would be very useful to have end-to-end test for like he proposed. So, please add a functional test and don't hesitate to contact me if you need any help on this.

Thank you! I will!

[cnasikas]

@elasticmachine merge upstream

[cnasikas]

@elasticmachine merge upstream

[gmmorris]

LGTM

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: eb65783

Metrics [docs]

distributable file count

id	value	diff	baseline
default	45848	+1	45847

History

• 💚 Build #77842 succeeded 7d0d45c
• 💔 Build #77210 failed 5dd2489
• 💔 Build #76844 failed 410940d
• 💚 Build #75840 succeeded 9cfa8371097bd541e313fa55ffb8a2da27980a08

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream