-
Notifications
You must be signed in to change notification settings - Fork 767
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
Add missing pvname #250
base: master
Are you sure you want to change the base?
Add missing pvname #250
Conversation
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
This adds the ability to use the pvname as part of the pathpattern. The defaultpath is now a string that is parsed the same way as the user specified pathpattern.
626e372
to
b47ac8e
Compare
updated branch to latest release and rebased code on top of that. |
} | ||
|
||
parsedPath := metadata.stringParser(pathPattern) | ||
if parsedPath == "" { |
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.
empty parsedPath means that the stringParser()
necessarily failed? or pathPattern may exist but empty as well?
and what can cause stringParser to fail, pathPattern such as foo-${.nonexistingvar}
? in such case stringParser()
will return empty string?
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.
the stringParser()
will return "" only if none of the patterns match. The tricky part is that if the pattern is ${.nonexisting1}-${.nonexisting1}
the parsedPath will be -
, and will not be captured by the error and all nfs paths will be mapped to just -
/ok-to-test |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
It would be nice to see this merged in. |
Will look at the comments, and fix the PR |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: robkooper The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Is there plans to merge this change cause i'm very interested in having this variable accessible for setting pathPatern? nfs-subdir-external-provisioner/cmd/nfs-subdir-external-provisioner/provisioner.go Line 90 in a398074
|
also waiting for this one |
I'm also waiting, please merge ASAP |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
This relates to issue #149 and allows to use the PVName in the path pattern. This adds the ability to use the pvname as part of the pathpattern, the same way that is done in the default pattern. The default path pattern is now a string that is parsed the same way as the user specified pathpattern.
This addresses the issues in PR #157. I decided to start clean to address those issues, hence a new PR.