search

shinesolutions / aem-orchestrator

Java application for orchestrating AEM infrastructure created using aem-aws-stack-builder
Apache License 2.0
12 stars 9 forks source link

Use AEM Healthcheck URL to verify if Publish is healthy #59

Open mbloch1986 opened 3 years ago

mbloch1986 commented 3 years ago

When we introduced the new EC2 Tag COMPONENT_INIT_STATUS to identify if the provisioning of the EC2 instance finished successful. We've replaced the existing Publisher healthcheck logic in the orchestrator to use this EC2 tag for verification.

Ideally we should use both to identify if the Publisher is healthy or not.

The Commit where we replaced the healthcheck logic: https://github.com/shinesolutions/aem-orchestrator/commit/a5eee904fec3d2951b1bf15ba2a4abceb48d459f

mbloch1986 commented 3 years ago

On top of verify if the provisioning was successful & the healthcheck returns the response code 200 we should also verify if the replication agent queue on the AEM Author instances are empty via the AEM Healthcheck URL. This will allow us to determine if the replication queue contains items or not.