Skip to content

topology.go uses bare 503 literal with no named constant inconsistent with other handlers #7795

@aashu2006

Description

@aashu2006

User Request

Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 2f570c9c-637f-4a47-948a-e5bacdfe4da3

Description

What happened:
In pkg/api/handlers/topology.go:76, c.Status(503) is a bare integer literal with no named constant. Every other similar handler (crds.go, admission_webhooks.go, service_exports.go) defines a statusServiceUnavailableXxx = 503 constant first.

What I expected:
A named constant statusServiceUnavailableTopology = 503 should be defined and used consistent with other handlers.

Steps to reproduce:

  1. Review topology.go:76 and compare with crds.go:63 and admission_webhooks.go:60
  2. Observe the inconsistent bare literal

This issue was automatically created from the KubeStellar Console.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ai-fix-requestedai-processingAI is currently processing this issuekind/bugCategorizes issue or PR as related to a bug.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions