feat: update synthetics implementation according to Kibana 8.16 API changes #967
+732
−233
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
This pr
ssl_certificate_authorities
,ssl_certificate
,ssl_key
andssl_key_passphrase
to synthetics monitors (tcp
andhttp
). Related to [Feature] Support option ssl.certificate_authorities for elasticstack_kibana_synthetics_monitor #916alert
field of a monitorCONTRIBUTING.md
, as a first step towards to [Bug] Add contributor docs #826Warning
ssl_certificate_authorities
works only from8.16.0
due-to elastic/kibana#187952Note due-to fixes in
8.16
/ #964 we can now importpassowrd
fields from kibana (marked as sensitive in this PR).TODO