fix: resolve incorrect binary path for docker hub based images #86
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- see if this will help with the random disconnects
- Not necessarily better, but was more clear for the export and kubeconfig input, so I'm just flipping to that to see if it helps with workflow. Can toggle easily with kind if desired.
|
👉 Note, there are some integration test failures for json that is maintenance to improve and being tracked in AB#480669. Additionally some other scan info should be overriden as we aren't going to patch major kubernetes library versions at this time as it's breaking changes not normal patch level changes. |
|
approving as the same test issue isn't related to this fix which is important to get out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This isn't confirmed resolved as not sure if vscode configuration issue, codespaces issue, or something else causing this.
Local development works fine, but container based workspaces seem to have timeouts randomly.