With the introduction of the provider certification workflow for end users, they have the power to validate their own CAPI providers. For certain providers that we may not be able to verify or simply don't have time to do so, we can have a subsequent request process that, after user certification, allows them to create a formal request to have the user-certified provider added the Certification Table we have in the docs. This means this user-certified provider will be added to our own set of tests and will become actively tested. This can help us identify new providers that users are using and we can leverage their work on certifying them to have them in our CI checks.
Turtles developers can assess whether the request can be accepted or not once published.
Description
With the introduction of the provider certification workflow for end users, they have the power to validate their own CAPI providers. For certain providers that we may not be able to verify or simply don't have time to do so, we can have a subsequent request process that, after user certification, allows them to create a formal request to have the user-certified provider added the Certification Table we have in the docs. This means this user-certified provider will be added to our own set of tests and will become actively tested. This can help us identify new providers that users are using and we can leverage their work on certifying them to have them in our CI checks.
Turtles developers can assess whether the request can be accepted or not once published.
This is linked to https://github.com/rancher/turtles-docs/issues/136