-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Create port map on container config if empty #6621
Conversation
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 need to remove this emtpy deploy_test.go though
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.
Remove empty file.
c9a591d
to
06d02e7
Compare
@briandealwis @tejal29 I had intentionally left that blank file here as a reminder that test cases needed to be added (so CI would fail until they were), but I realized that there were existing (broken) test cases for this. they're now fixed and this should be ready for a look |
Codecov Report
@@ Coverage Diff @@
## main #6621 +/- ##
==========================================
- Coverage 70.48% 70.13% -0.35%
==========================================
Files 515 520 +5
Lines 23150 23614 +464
==========================================
+ Hits 16317 16562 +245
- Misses 5776 5973 +197
- Partials 1057 1079 +22
Continue to review full report at Codecov.
|
This was causing a nil pointer exception when the container didn't have previously defined ports in its config.
This was not caught by tests because these tests were actually silently broken - a
debug
level log message was being emitted saying these port forward resources were being skipped because they were not of resource typecontainer
. Upon adding this to the tests cases, this test failed as expected.