fix kustomize path for big-bang core package #508
Merged
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
YrrepNoj
approved these changes
Jun 9, 2022
|
Good package creation now: Working package deploy options: Successful package deployment: Helm releases pulled from gitea: |
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.
A small typo was introduced with the big bang core example -> packages move in #488, this corrects that. Since we do not have the ability to run this in E2E right now due to IB credentials and how SUPER long it would take to fully test, including screenshots in the PR after testing from M1 -> Ubuntu AMD64 remote machine using https://github.com/alexellis/k3sup.
note from PR author: this was the first (and one of the only times) I had used k3sup, because I wanted to try it as an alternative to my code-server setup I had been using for a year. Based on the citation of this note in a closed PR on that project, leaving a clarifying note here, this was an isolated local test, and k3sup is no longer used.