Web terminal: fix warning when sourcing .bashrc#6848
Web terminal: fix warning when sourcing .bashrc#6848kubermatic-bot merged 1 commit intokubermatic:mainfrom
Conversation
Since Helm 3.3.3, warning messages are displayed when the KUBECONFIG permissions are group/world readable. helm/helm#8779 writes them to stderr. The warnings are displayed when opening the web terminal, as 'helm completion' execs when the .bashrc is sourced. Signed-off-by: Samuel Alfageme Sainz <samuel@alfage.me>
|
Hi @SamuAlfageme. Thanks for your PR. I'm waiting for a kubermatic 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. |
|
Should I also bump the ... or would you rather bundle it with more features? |
We can move ahead with this PR as is, let me re-evaluate if other dependencies need to be updated as well for web terminal in a follow-up PR. Thanks for the contribution 🎊 |
|
LGTM label has been added. DetailsGit tree hash: 92490ca8921d0d23d806f859bae82a61a6a6a634 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik 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 |
|
/ok-to-test |
)" This reverts commit 5d1ec10. Signed-off-by: Samuel Alfageme Sainz <samuel@alfage.me>
What this PR does / why we need it:
Since Helm 3.3.3, warning messages are displayed when the KUBECONFIG permissions are group/world readable. helm/helm#8779 writes them to stderr.
The warnings are displayed when opening the web terminal, as 'helm completion' execs when the .bashrc is sourced:
... this confuses unexperienced users.
What type of PR is this?
/kind enhancement
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: