[➕ Feature]: hide unused configuration fields for provisioned providers

[gecube]

Summary

When a provider is configured via the provision mechanism (i.e. its parameters are supplied declaratively through Helm values or YAML and cannot be modified via the UI), the interface still displays editable form fields that are irrelevant in this context.

For example, when the FluxCD provider is configured using an in-cluster configuration (only namespace is defined), the UI still shows multiple Kubernetes connection fields that do not apply.

---

🧩 Example configuration

backend:
  provision:
    providers:
      fluxcd:
        type: fluxcd
        authentication:
          namespace: flux-system

In this setup, the provider is fully defined in configuration, not editable from the UI — which is correct and expected.

However, the UI still displays the following fields:

• Kubeconfig file content
• Kubernetes context to use
• Kubernetes API server URL
• Kubernetes API token
• Skip TLS verification

These fields contain placeholder values like “Enter token” or “Enter kubeconfig”, which is confusing and redundant.

---

💡 Expected behavior

If a provider is provisioned via values.yaml or other declarative mechanism:

• The UI should hide or disable configuration fields that cannot be edited.
• Only display the fields that are actually used in the current provisioning mode (e.g. namespace for in-cluster configuration).

---

✅ Benefits

• Cleaner and more intuitive interface
• Prevents user confusion and false impression that credentials can be edited
• Reduces UI clutter for provisioned integrations
• Reinforces clear separation between “UI-managed” and “Helm-managed” providers

---

🧠 Possible implementation

• Check provider configuration source (UI vs provisioned)
• Dynamically adjust visible input fields
• Disable “Save” button for provisioned providers to indicate they are read-only

---

Labels: type:enhancement area:ui priority:medium