-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve registry validation #1429
Conversation
) | ||
if not provider_instance.registry or not image.startswith( | ||
raise ValidationError(f"{provider} is not valid provider.") | ||
if provider_instance.registry and not image.startswith( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we sure here that provider_instance
always has registry
attribute?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you mean if the registry
from provider_instance
can be None
? The answer is yes. What I'm trying to do here is that if it's None
it's ok, we accept any value in the image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Until now we were forcing it to have a value but there are situations where it can has no sense like in local development.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Applied #1429 in 0.14 * Update 0.14 patch version * Updated helm lock
Summary
Fix #1428
Let's simplify the logic of the registry validation to allow that if a registry is not specified the provider can use any registry that it wants. Specifically useful for development.