-
Notifications
You must be signed in to change notification settings - Fork 174
Improve func build/deploy UX: validate registry before prompting #3058
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 func build/deploy UX: validate registry before prompting #3058
Conversation
|
Hi @RayyanSeliya. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3058 +/- ##
==========================================
+ Coverage 57.68% 59.12% +1.44%
==========================================
Files 133 134 +1
Lines 17120 17218 +98
==========================================
+ Hits 9875 10180 +305
+ Misses 6343 6078 -265
- Partials 902 960 +58
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
PTAL @gauron99 when you have some moments ! |
gauron99
left a comment
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.
just a few suggestions
gauron99
left a comment
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 the PR! i left some comments
…eploy and also refactor the logic when ran outside the function directory using 2 layer approach Signed-off-by: RayyanSeliya <rayyanseliya786@gmail.com>
Signed-off-by: RayyanSeliya <rayyanseliya786@gmail.com>
…irst Signed-off-by: RayyanSeliya <rayyanseliya786@gmail.com>
Signed-off-by: RayyanSeliya <rayyanseliya786@gmail.com>
… different file for better code readability and also add the platformrestriction error i lost while rebasing Signed-off-by: RayyanSeliya <rayyanseliya786@gmail.com>
807a4aa to
395a661
Compare
lkingland
left a comment
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
|
/ok-to-test |
|
/retest |
|
/test unit-tests |
|
/override ? |
|
@gauron99: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
There is a very strange IPV6 error which happens across PRs, completely unrelated to this. Overriding the unit test to not block PR |
|
@gauron99: Overrode contexts on behalf of gauron99: unit-tests_func_main DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gauron99, lkingland, RayyanSeliya The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
/kind enhancement
Fixes #3057
Solution:
Validate the missing registry error first before asking for a registry prompt! Use a 2-layer approach as discussed!
Implementation Details:
func buildandfunc deploycommands to validate registry requirement before promptingRelease Note