Add sample to use updatecli to update mysql image

[jsoriano]

Try to use updatecli to automatically update mysql variant image.

Related to elastic/elastic-package#1902.

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 4847566

Failed CI Steps

• Check integrations atlassian_confluence
• Check integrations azure_blob_storage
• Check integrations cisco_aironet
• Check integrations istio
• Check integrations memcached
• Check integrations nats
• Check integrations pps
• Check integrations qnap_nas
• Check integrations slack
• Check integrations symantec_edr_cloud
• Check integrations ti_maltiverse
• Check integrations ti_mandiant_advantage
• Check integrations ti_util
• Check integrations windows_etw
• Check integrations zerofox
• Check integrations zeronetworks
• Check integrations zscaler_zpa

History

• 💔 Build #14138 failed 39a1306

cc @jsoriano

[jsoriano]

@shmsr added a couple of comments highlighting the parts that would be more relevant to manage each version upgrade. The rest is mostly boilerplate.

[jsoriano]

Following this approach, an entry like this one would be needed for any service. We could try to find some way to run all the configs at once.

[jsoriano]

This source and target would be the main part to configure for every version to upgrade.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[botelastic]

Hi! We just realized that we haven't looked into this PR 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!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!