Problem:
Currently, there needs to be a way to specify container registries (Azure, Google, DockerHub, Amazon, others?) host/login/password in TES configuration.
Solution 1 :
Review whether this should be added to the TES spec. Maybe add to Resources section or consider backend_parameters. Consult with @vsmalladi
Solution 2:
Add a TES config section to be able to supply a list of the tuple:
Validate that all properties of the tuple contain a value at startup, and throw an exception if not and TES shall not start.
Consider whether there are additional properties needed to support the following container registry providers: (Azure, Google, DockerHub, Amazon, others?).
TES shall parse the image name to determine whether the container credentials were provided in configuration, and if so, it shall use the provided credentials to connect.
Problem: Currently, there needs to be a way to specify container registries (Azure, Google, DockerHub, Amazon, others?) host/login/password in TES configuration.
Solution 1 :
Solution 2:
"ContainerRegistryHostname", "ContainerRegistryLogin", "ContainerRegistryPassword"