🚀 Feature: support declarative configuration of OIDC clients #62

Closed
opened 2025-10-07 23:51:24 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @a-bali on GitHub.

Feature description

Instead of requiring that OIDC clients are manually created using the web interface, support defining them in a configuration file i.e. declaratively.

Alternative idea: implement a Kubernetes generator that takes ConfigMaps as input and sets up OIDC clients as output.

Pitch

This would enable full compatibility with the GitOps approach so that all configuration and instructions for a Kubernetes cluster can be defined declaratively and executed without need for manual intervention.

Originally created by @a-bali on GitHub. ### Feature description Instead of requiring that OIDC clients are manually created using the web interface, support defining them in a configuration file i.e. declaratively. Alternative idea: implement a Kubernetes generator that takes ConfigMaps as input and sets up OIDC clients as output. ### Pitch This would enable full compatibility with the GitOps approach so that all configuration and instructions for a Kubernetes cluster can be defined declaratively and executed without need for manual intervention.
Author
Owner

@stonith404 commented on GitHub:

While we don't support it officially, this should already be possible with the Terraform provider, see https://github.com/pocket-id/pocket-id/issues/689.

@stonith404 commented on GitHub: While we don't support it officially, this should already be possible with the Terraform provider, see https://github.com/pocket-id/pocket-id/issues/689.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-1#62