fix: [M3-8912] - Create support ticket for buckets created through legacy flow - Githubissues

linode / manager

Akamai's Cloud Manager is an open-source, single-page application designed as the primary frontend interface for interacting with the Linode API. It is entrusted by hundreds of thousands of customers with the management of their Linode services.

https://cloud.linode.com

Apache License 2.0

700 stars 363 forks source link

fix: [M3-8912] - Create support ticket for buckets created through legacy flow #11300

Open harsh-akamai opened 1 week ago

harsh-akamai commented 1 week ago

Description 📝

This PR addresses 2 errors during the ObjectStorage Support Ticket creation flow:

If an account has multiple buckets in the same region/cluster, the Create Support Ticket workflow reads only the first bucket.
An error occurs when attempting to create a Support Ticket for a bucket that was created using the legacy flow (buckets created through clusters).

Changes 🔄

Added Support for buckets created through the legacy flow
Fixed the create flow for accounts that have multiple buckets in the same region/cluster

Target release date 🗓️

12/10

Preview 📷

Before

https://github.com/user-attachments/assets/b268eeb1-897d-4c33-9c08-9abe2d70e97f

How to test 🧪

Prerequisites

Turn on legacy flow for Object Storage (Check internal ticket for customer tags)
Test this in the dev environment to avoid bothering Customer Support with real tickets

Reproduction steps

[ ] Creating an Object Storage Support ticket from an account that has multiple buckets in the same region/cluster picks only the first bucket as shown in preview video
[ ] Submitting an Object Storage Support ticket form an account that has legacy flow present throws an error as shown in the preview

Verification steps

[x] Ensure an Object Storage Support ticket can be created in both scenarios pointed out

As an Author, I have 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

[x] I have read and considered all applicable items listed above.

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

[x] All unit tests are passing
[x] TypeScript compilation succeeded without errors
[x] Code passes all linting rules

linode-gh-bot commented 1 week ago

Cloud Manager UI test results

:small_red_triangle: 3 failing tests on test run #1 ↗︎

:x: Failing	:white_check_mark: Passing	:arrow_right_hook: Skipped	:clock1: Duration
`3 Failing`	`451 Passing`	`2 Skipped`	`112m 28s`

Details

Failing Tests
	Spec	Test
:x:	`linode-storage.spec.ts`	linode storage tab » delete disk
:x:	`linode-storage.spec.ts`	linode storage tab » add a disk
:x:	`linode-storage.spec.ts`	linode storage tab » resize disk

Troubleshooting

Use this command to re-run the failing tests:

yarn cy:run -s "cypress/e2e/core/linodes/linode-storage.spec.ts,cypress/e2e/core/linodes/linode-storage.spec.ts,cypress/e2e/core/linodes/linode-storage.spec.ts"