-
Notifications
You must be signed in to change notification settings - Fork 772
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
customize resource name individually via labels kompose.service.name_override #1837
Conversation
…ame_override Signed-off-by: jose luis <[email protected]>
Thanks @sosan, I would review this once the other PR is merged! |
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
/approve |
Signed-off-by: jose luis <[email protected]>
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cdrage, sosan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
this PR is the second part from #1833 and suggests labels to allow individual customization. Uses
kompose.service.name_override
label, but can change label nameWhich issue(s) this PR fixes:
Feature #1635
Special notes for your reviewer:
tests
Test_parseKomposeLabels
encounters a corner case scenario where the resource name that being processed starts or ends with a hyphen '-' or any other character// This is a corner case that is expected to fail because
// it does not account for scenarios where the string
// starts or ends with a '-' or any other character
// this test will fail with current tests