[Uptime] [Synthetics Integration] fall back to checking verification mode to determine if tls is enabled

[dominiqueclarke]

Summary

Fixes #115009

The Elastic Synthetics integration must provide backwards compatibility for integration policies created in earlier versions, because Fleet will not ship with auto upgrading package policies for the Elastic Synthetics integration until 8.1.0.

To support this backwards compatibility, #114914 was added to ensure that older policies are able to be upgraded to the most recent package version when editing. This resolves 99% of the compatibility issues.

However, we also changed the way we handle determining whether or not TLS is enabled during the package policy edit flow. This PR resolves those issues.

In 7.16, we added new logic to put a key onto the integration policy to determine if TLS had been enabled. This new key is used exclusively by the UI, not heartbeat, in order to render the TLS toggle as checked in the edit integration flow. That key is __ui.is_tls_enabled and __ui.is_zip_url_tls_enabled for normal http/tcp tls and for Zip URL tls, respectively.

However, policies created earlier than than 7.16 will not have this key. In order to support backwards compatibility, we check if ssl.verification_mode has been added the policy as a back up.

In reality, adding these new __ui keys for tls was not necessary and were added prematurely. The truth presence of ssl.verification_mode is sufficient way to check if tls has been abled for that policy, because ssl.verification_mode is always defined on every policy that has ssl enabled.

I don't feel comfortable removing the new __ui.is_tls_enabled and __ui.is_zip_url_tls_enabled after feature freeze, as it's working as expected for new policies. However, we should consider removing this in 8.0.0, as it's extra, unnecessary logic.

Testing

1. Pull down this branch
2. Change your Kibana port to 5602
3. Start Kibana
4. Run elastic-package stack up --version 8.0.0-SNAPSHOT -v
5. Once elastic-package is up, run curl -u elastic:changeme -X POST "http://localhost:9200/_security/user/kibana_system/_password?pretty" -H 'Content-Type: application/json' -d' { "password" : "changeme" } '
6. Login to localhost:5602
7. Navigate directly to the synthetics integration on an old, pre-7.16 policy version by visiting http://localhost:5602/axi/app/integrations/detail/synthetics-0.3.0/overview
8. Create an HTTP monitor and enable TLS
9. Go to edit that HTTP monitor
10. Verify that TLS is enabled within the edit flow

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[dominiqueclarke]

@elasticmachine merge upstream

[dominiqueclarke]

@elasticmachine merge upstream

[dominiqueclarke]

@elasticmachine merge upstream

[shahzad31]

LGTM, Tested locally !!

[dominiqueclarke]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: d2eb49c
• Storybooks Preview

Test Failures

• [job] [logs] OSS CI Group #9 / management scripted fields preview should display script results when script is valid
• [job] [logs] Default CI Group #6 / Uptime app with real-world data uptime alerts overview page alert flyout controls posts an alert, verifies its presence, and deletes the alert

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
uptime	574.1KB	574.3KB	+176.0B

History

• 💚 Build #6736 succeeded b87732b
• 💚 Build #5906 succeeded 7f895e1
• 💚 Build #5107 succeeded fc4100c
• 💚 Build #3744 succeeded 1117d62

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

[kibanamachine]

The following labels were identified as gaps in your version labels and will be added automatically:

• v8.1.0

If any of these should not be on your pull request, please manually remove them.

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	8.0
✅	7.16

The backport PRs will be merged automatically after passing CI.