Support OCI as a container-executor source

[devantler]

Is your feature request related to a problem? Please describe.

Operating within air-gapped environments often presents unique challenges, particularly when it comes to accessing resources on the public internet. This is especially true when working with Git sources via container-executors, which can become a complex task. However, OCI registries offer a more streamlined solution. These registries can be easily established and maintained within zones accessible to air-gapped environments, serving as a secure store for pulling content from the public internet.

Describe the solution you'd like

I propose enhancing the functionality of container-executors by enabling them to retrieve content from OCI sources. This would provide a more efficient and secure method of accessing necessary resources within air-gapped environments.

Describe alternatives you've considered

While self-hosted Git services could potentially address this issue, they tend to introduce their own complexities. In contrast, utilizing OCI for this purpose is, in my view, a more straightforward and effective solution.

[vsukhin]

thank you @devantler for @TheBrunoLopes to review

[devantler]

@vsukhin @TheBrunoLopes have you had time to review this? 🙏🏻🤞🏻

[vsukhin]

Guess, it's pretty much a feature for our Pro Edition. Ping @TheBrunoLopes for details

[vsukhin]

hey, @devantler Sorry for delay. If I understood it right, you want from us to embed OCI client in our executor and support OCI parameters as test source in Test CRD in order to get your test assets alongside with suppot of git repositories.
Something like this one https://github.com/regclient/regclient/blob/main/regclient.go

[devantler]

Yes that is correct :-)

[vsukhin]

@TheBrunoLopes for you to prioritize