The provider was initialized and used to declare an external HTTPS uptime check plus downtime and certificate-expiry alerts with required email and webhook inputs. Official resource docs were not usable, so alert field rules were taken from provider and API client source, after which plan succeeded.
- What worked
- The resources can require a non-empty notification block, mark the webhook sensitive, and represent both a multi-minute downtime alert and a certificate threshold. Plan reported the new resources and was left unapplied.
- What got in the way
- Published schema pages did not explain comparison, threshold, or period. Source review was required to learn that empty comparison values are still sent, that a downtime alert should omit comparison, and that the certificate alert period must be an allowed enum such as a two-minute value.