Skip to content
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

Add fish shell detection #789

Closed

Conversation

Qinusty
Copy link

@Qinusty Qinusty commented Aug 21, 2019

Implement basic shell detection for Linux platforms in the kind create command.

Additions:

  • Implement GetLinuxShell() utility function
  • Add fish as a custom output whilst leaving bash/zsh under default

@k8s-ci-robot
Copy link
Contributor

Welcome @Qinusty!

It looks like this is your first PR to kubernetes-sigs/kind 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kind has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Aug 21, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Qinusty
To complete the pull request process, please assign bentheelder
You can assign the PR to them by writing /assign @bentheelder in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Contributor

Hi @Qinusty. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 21, 2019
)

func GetLinuxShell() string {
shell := os.Getenv("SHELL")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if the user unset the SHELL variable, e.g. by mistake?

Copy link
Author

@Qinusty Qinusty Aug 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is currently a best guess, I'm not certain of a guaranteed way to get the users current shell. Scraping current running processes would run into a similar issue if the user was running multiple shells.

In regard to what would happen, shell would be "" and it would default and behave as it currently does without this logic.

@@ -190,12 +191,20 @@ func printUsage(name string) {
name,
)
} else {
// Detect shell and usage build prompt appropriately.
setKubeConfigPrompt := ""
switch shell := env.GetLinuxShell(); shell {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't the function be called UnixShell, as this branch is !windows?
can it cover custom OSX shells too?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also noting that fish appears to be on macOS

@neolit123
Copy link
Member

thanks for the PR @Qinusty

please make sure you sign the CLA if this command fails:
/check-cla

@neolit123
Copy link
Member

if you have signed the CLA already, make sure your CLA email is added to your github account.
if there is a problem with that try contacting the CNCF help-desk.

WRT this PR, i must admit this is the first time i've heard about "fish" shell, and given all the flavors of shells out there, it might be better to not add special handling for all of them?
/assign @BenTheElder

setKubeConfigPrompt := ""
switch shell := env.GetLinuxShell(); shell {
case "fish":
setKubeConfigPrompt = "set -x KUBECONFIG (kind get kubeconfig-path --name=%q)"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit dumbfounded that a Linux shell doesn't support POSIX... 🧐
https://pubs.opengroup.org/onlinepubs/009695399/utilities/export.html

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it's a bit strange but it appears to be the case. https://fishshell.com/docs/current/tutorial.html#tut_exports

@BenTheElder
Copy link
Member

#850 landed so we don't need to export this env anymore.

Thanks for the PR though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants