docs: update event notifications for instance upgrade lifecycle events#3891
docs: update event notifications for instance upgrade lifecycle events#3891AmberAlston merged 3 commits intomainfrom
Conversation
…vents Reflects changes from vandoor PR #9180: - Rename Instance Upgraded to Instance Upgrade Started with updated description - Add new Instance Ready event (fires once when app status first becomes ready) - Add new Instance Upgrade Completed event (fires when app is ready after upgrade) - Update Instance Created description to "sends its first check-in" - Update webhook payload example to use instance.upgrade_started - Update license field condition filters list with new event names Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| - **Instance Upgrade Completed**: When an instance's application status is Ready after upgrading to a new release version | ||
| - **Instance Version Behind**: When an instance falls behind by a specified number of versions | ||
| - **Instance Inactive**: When an instance has not reported in for 24 hours (declared "Inactive"). Air-gapped instances are excluded from this event type. | ||
| - **Instance Inactive**: When an instance has not reported for 24 hours (declared "Inactive"). Air-gapped instances are excluded from this event type. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('are excluded').
| - **Instance Upgrade Completed**: When an instance's application status is Ready after upgrading to a new release version | ||
| - **Instance Version Behind**: When an instance falls behind by a specified number of versions | ||
| - **Instance Inactive**: When an instance has not reported in for 24 hours (declared "Inactive"). Air-gapped instances are excluded from this event type. | ||
| - **Instance Inactive**: When an instance has not checked-in for 24 hours (declared "Inactive"). Air-gapped instances are excluded from this event type. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('are excluded').
paigecalvert
left a comment
There was a problem hiding this comment.
thank you looks good!
| - **Instance Upgraded**: When an instance upgrades to a new release version | ||
| - **Instance Created**: When a new instance sends its first check-in | ||
| - **Instance Ready**: When a new instance's application status is Ready for the first time | ||
| - **Instance Upgrade Started**: When an instance begins upgrading to a new release version. This event fires when the Vendor Portal receives the first telemetry with a new release version, whether or not the application status is Ready. |
There was a problem hiding this comment.
note: I ended up editing out the passive voice here, but mainly because I wanted to reword the second sentence for clarity anyway.
| - **Instance Upgrade Completed**: When an instance's application status is Ready after upgrading to a new release version | ||
| - **Instance Version Behind**: When an instance falls behind by a specified number of versions | ||
| - **Instance Inactive**: When an instance has not reported in for 24 hours (declared "Inactive"). Air-gapped instances are excluded from this event type. | ||
| - **Instance Inactive**: When an instance has not checked-in for 24 hours (declared "Inactive"). Air-gapped instances are excluded from this event type. |
There was a problem hiding this comment.
We typically use "check-in" rather than "report in" to talk about an instance being active or inactive
| - **Instance Created**: When a new instance is created | ||
| - **Instance Upgraded**: When an instance upgrades to a new release version | ||
| - **Instance Created**: When a new instance sends its first check-in | ||
| - **Instance Ready**: When a new instance's application status is Ready for the first time |
There was a problem hiding this comment.
When a new instance's application status is Ready
I've capitalized mentions of a "Ready" status because it's referring to the status' name (proper noun) versus just the word ready.
Preview link: https://deploy-preview-3891--replicated-docs-upgrade.netlify.app/vendor/event-notifications-create#instance-events
Summary
Updates Event Notifications docs to reflect changes from vandoor PR #9180:
instance.upgrade_startedTest plan
🤖 Generated with Claude Code