upcoming: [M3-10674] - Add pendo ids for VM analytics

[jaalah-akamai]

Description 📝

Implements Pendo tracking tags for VM Host Maintenance Policy feature to monitor user interactions and gather analytics.

Changes 🔄

• Added data-pendo-id to several areas for VM Host Maintenance
• Added ability to add custom pendo id's to <Link> component
• "Learn more" links also have pendo id's (not shown in screenshots below)

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Target release date 🗓️

10/21

Preview 📷

File	Screenshot
Autocomplete, options, and account save button with id's
Linode Details - Save Button
Banners: Linode, Platform, Regular Maintenance

|

How to test 🧪

Reproduction steps

• In your local environment on develop
• Choose a linode you have on your account, copy it's linode id
• Open our dev-tools, enable MSW, and under "Presets" enable "Maintenance"
• Edit the "Maintenance" preset
• In the JSON editor, copy this object and replace the: id, label, and url with your chosen linode

[
  {
    "entity": {
      "id": <ADD_LINODE_ID>,
      "label": "<ADD_LINODE_LABEL>",
      "type": "linode",
      "url": "/v4/linode/instances/<ADD_LINODE_ID>"
    },
    "maintenance_policy_set": "linode/migrate",
    "reason": "We must replace faulty RAM in your Linode's host.",
    "description": "emergency",
    "source": "user",
    "status": "scheduled",
    "type": "live_migration",
    "when": null,
    "not_before": null,
    "start_time": null,
    "complete_time": null
  }
]

Platform Notification

• Follow similar steps for Notifications preset
• Choose "Add from template" > "Platform Maintenance Scheduled"
• Add in linode id's
• Ensure dates are in future

Verification steps

• For Banners, follow reproduction steps above and you should see banners in linodes landing page.
• For other changes to Maintenance Policy Select, find the component on:
  • /linodes/create/os
  • /linodes/<linode_id>/settings
  • /account-settings

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[dwiley-akamai]

Code review ✅
Verification steps ✅

The E2E tests that failed seem a bit flaky; I ran them a few times locally and the failures were inconsistent.

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #5 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	840 Passing	11 Skipped	39m 6s

Details

Failing Tests
	Spec	Test
❌	timerange-verification.spec.ts	Cloud Manager Cypress Tests→Integration tests for verifying Cloudpulse custom and preset configurations » should implement and validate custom date/time picker for a specific date and time range

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/cloudpulse/timerange-verification.spec.ts"