Expand the enum of `status` in `check_external_connection` in Account API

[shirady]

Environment info

• NooBaa Version: 5.23
• Platform: Doesn't matter

Actual behavior

1. Currently, the API of check_external_connection does not contain an enum for the case where the user / service account has permission issue with the list buckets, and it uses this list:
   

   noobaa-core/src/api/account_api.js

   Lines 532 to 544 in 130f763

   	properties: {
   	status: {
   	type: 'string',
   	enum: [
   	'SUCCESS',
   	'TIMEOUT',
   	'INVALID_ENDPOINT',
   	'INVALID_CREDENTIALS',
   	'NOT_SUPPORTED',
   	'TIME_SKEW',
   	'UNKNOWN_FAILURE'
   	]
   	},

   
   Note: In GCP and GCP WIF (STS) we return the INVALID_CREDENTIALS status for this case.

Expected behavior

1. Expand this list with the enum related to the permissions.

Steps to reproduce

1. Create the details for the client to test without permission for list buckets
2. Test the API and check the status

More information - Screenshots / Logs / Other output

In this link, you can see the exact steps that were done for GCP WIF (STS) to test the permission and the API of check_external_connection.

[coderabbitai]

🔗 Related PRs

#9291 - IAM | No Bucket Policy Authorization for IAM Users [merged]
#9301 - Fix (NC | NSFS) - list_buckets allowing unauthorized bucket access [merged]
#9307 - IAM | User Without IAM User Policy Improve Error Message [merged]
#9316 - Added support for iam user in list_buckets() for containerized [merged]
#9641 - STS | Azure error code check for connevction [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[shirady]

@coderabbitai I raised it after I tested PR #9644 and it does not appear on your list.

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch details about PR `#9644`
gh pr view 9644 --repo noobaa/noobaa-core --json number,title,state,url,body,labels,mergedAt

Length of output: 5302

---

🏁 Script executed:

#!/bin/bash
# Fetch details about issue `#9665`
gh issue view 9665 --repo noobaa/noobaa-core --json number,title,state,url,body,labels

Length of output: 1379

---

---

@shirady, thank you for the clarification! PR #9644 (GCP WIF (STS) | Updated Enums and Consts and Create GCP Client) is indeed directly related — the issue was discovered while testing that PR, and the steps to reproduce link back to its comment thread. It wasn't included in the auto-generated list because it was still open at the time (the auto-detection tends to surface already-merged PRs).

Here is the updated related PRs list for reference:

PR	Title	Status
#9291	IAM | No Bucket Policy Authorization for IAM Users	merged
#9301	Fix (NC | NSFS) - list_buckets allowing unauthorized bucket access	merged
#9307	IAM | User Without IAM User Policy Improve Error Message	merged
#9316	Added support for iam user in list_buckets() for containerized	merged
#9641	STS | Azure error code check for connection	merged
#9644	GCP WIF (STS) | Updated Enums and Consts and Create GCP Client	open