Description

The goal is to create a credential system that is going from map[string]string into Typed system that can self-document itself and makes it easier to discover usable identities for consumers and credential providers.

User Story
As a usr of ocm, I want to have clearly defined spec how to provide credentials an in what form.
As a maintainer of ocm, I want to have validation of credentials where they are consumed by a versioned spec and a clearly defined api.
As a user, I want that my current credential configuration will work with the new typed system, as long as they are valid.

Scope
List all deliverables that are part of this epic. The Epic is considered DONE if all of the below mentioned deliverables are available.

• ADR about the new credential system
• Ways to deliver common credentials for our built-in systems
• Ways to extend the registered credentials for plugins and other systems that are yet to be defined
• Ways to have several versions of a credential type for compatibility
• Credential aware apis like repository, plugins etc, where the currently might have tech debt to support the new system

Out of Scope
List features or implementation strategies that shouldn't be considered in this iteration.