[Feature]: Option to disable a key without deleting it.

[sammaji]

Prerequisites

• I have searched existing issues and discussions to avoid duplicates

Problem to solve

We can add an option to disable a key.

Proposed solution

Maybe a toggle switch here.

Alternatives considered

No response

Area(s)

Transports (HTTP), UI (Next.js), Core

Additional context

No response

[slyang08]

Hi @sammaji ,
Can I take this issue?

[Pratham-Mishra04]

Yes sure, assigning it to you😄

[slyang08]

Hi @Pratham-Mishra04 ,
I would like to confirm that this issue just need to make the key able/unable to edit on frontend, or should I also make a bit change for the backend?

[Pratham-Mishra04]

The idea is to introduce a “disabled” toggle for each key in the key configuration sheet. When a key is marked as disabled, it should be excluded from the key-selection algorithm.

To support this, we’d need to:
• Update key schema in core/schemas.go and the key selection algorithm in core/bifrost.go
• Add the new field to the keys table in framework/configstore
• Modify handler/providers.go to account for the disabled flag
• Implement the corresponding UI changes

Happy to clarify anything or discuss further!

[slyang08]

Thank you for the response, and I am confused about,
Is the key schemas in core/schemas/account.go instead of core/schemas.go

type Key struct {
	ID               string            `json:"id"`                           // The unique identifier for the key (used by bifrost to identify the key)
	Name             string            `json:"name"`                         // The name of the key (used by users to identify the key, not used by bifrost)
	Value            string            `json:"value"`                        // The actual API key value
	Models           []string          `json:"models"`                       // List of models this key can access
	Weight           float64           `json:"weight"`                       // Weight for load balancing between multiple keys
	AzureKeyConfig   *AzureKeyConfig   `json:"azure_key_config,omitempty"`   // Azure-specific key configuration
	VertexKeyConfig  *VertexKeyConfig  `json:"vertex_key_config,omitempty"`  // Vertex-specific key configuration
	BedrockKeyConfig *BedrockKeyConfig `json:"bedrock_key_config,omitempty"` // AWS Bedrock-specific key configuration
}

[Pratham-Mishra04]

Yes my bad, that’s what I meant