Skip to content

docs: update event notifications for instance upgrade lifecycle events#3891

Merged
AmberAlston merged 3 commits intomainfrom
event-notifications-upgrade-events-clean
Mar 17, 2026
Merged

docs: update event notifications for instance upgrade lifecycle events#3891
AmberAlston merged 3 commits intomainfrom
event-notifications-upgrade-events-clean

Conversation

@AmberAlston
Copy link
Copy Markdown
Member

@AmberAlston AmberAlston commented Mar 16, 2026

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:

  • Rename Instance Upgraded to Instance Upgrade Started -- clarifies it fires on first telemetry with new version, before the app is ready
  • 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 an upgrade
  • Update Instance Created description from "when a new instance is created" to "when a new instance sends its first check-in"
  • Update webhook payload example to use instance.upgrade_started
  • Update license field condition filters list with new event names

Test plan

  • Verify event type names match what ships in vandoor PR #9180
  • Verify descriptions accurately reflect event behavior
  • Check links and cross-references still work

🤖 Generated with Claude Code

…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>
@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 16, 2026

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit c887525
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/69b96c48f6e0340008bd5a9d
😎 Deploy Preview https://deploy-preview-3891--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link
Copy Markdown

netlify Bot commented Mar 16, 2026

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit c887525
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/69b96c48f6e0340008bd5aa1
😎 Deploy Preview https://deploy-preview-3891--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Mar 16, 2026
Comment thread docs/vendor/event-notifications-create.mdx Outdated
@AmberAlston AmberAlston marked this pull request as ready for review March 16, 2026 22:57
@AmberAlston AmberAlston requested a review from a team as a code owner March 16, 2026 22:57
- **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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('are excluded').

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ignoring

- **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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('are excluded').

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ignoring

Copy link
Copy Markdown
Contributor

@paigecalvert paigecalvert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@AmberAlston AmberAlston merged commit 7b32af5 into main Mar 17, 2026
5 checks passed
@AmberAlston AmberAlston deleted the event-notifications-upgrade-events-clean branch March 17, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants