-
Notifications
You must be signed in to change notification settings - Fork 385
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
registries.conf: prefixes: subdomain matching #1505
Conversation
LGTM |
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. Thanks!
docs/containers-registries.conf.5.md
Outdated
@@ -43,6 +43,8 @@ also include wildcarded subdomains in the format `*.example.com`. | |||
The wildcard should only be present at the beginning as shown in the formats | |||
above. Other cases will not work. For example, `*.example.com` is valid but | |||
`example.*.com`, `*.example.com/foo` and `*.example.com:5000/foo/bar:baz` are not. | |||
Note that `*` matches an arbitary number of subdomains. `*example.com` will hence | |||
match `bar.example.com`, `foo.bar.example` and so on. |
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.
match `bar.example.com`, `foo.bar.example` and so on. | |
match `bar.example.com`, `foo.bar.example.com` and so on. |
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.
Thanks for catching!
One nit, otherwise LGTM |
Mention that wildcarded prefixes match an arbitrary number of subdomains. Closes: containers#1397 Signed-off-by: Valentin Rothberg <[email protected]>
Mention that wildcarded prefixes match an arbitrary number of
subdomains.
Closes: #1397
Signed-off-by: Valentin Rothberg [email protected]
@mtrmac @rhatdan PTAL