From 735be12481cdc3edfcbca3500172d2164255e1a3 Mon Sep 17 00:00:00 2001 From: Valentin Rothberg Date: Fri, 2 Jul 2021 13:03:10 +0200 Subject: force github.com/spf13/cobra@v1.1.3 v1.2.0 is breaking CI (see containers/podman/pull/10844). Signed-off-by: Valentin Rothberg --- vendor/github.com/spf13/cobra/bash_completions.md | 2 -- 1 file changed, 2 deletions(-) (limited to 'vendor/github.com/spf13/cobra/bash_completions.md') diff --git a/vendor/github.com/spf13/cobra/bash_completions.md b/vendor/github.com/spf13/cobra/bash_completions.md index 52919b2fa..130f99b92 100644 --- a/vendor/github.com/spf13/cobra/bash_completions.md +++ b/vendor/github.com/spf13/cobra/bash_completions.md @@ -6,8 +6,6 @@ Please refer to [Shell Completions](shell_completions.md) for details. For backward compatibility, Cobra still supports its legacy dynamic completion solution (described below). Unlike the `ValidArgsFunction` solution, the legacy solution will only work for Bash shell-completion and not for other shells. This legacy solution can be used along-side `ValidArgsFunction` and `RegisterFlagCompletionFunc()`, as long as both solutions are not used for the same command. This provides a path to gradually migrate from the legacy solution to the new solution. -**Note**: Cobra's default `completion` command uses bash completion V2. If you are currently using Cobra's legacy dynamic completion solution, you should not use the default `completion` command but continue using your own. - The legacy solution allows you to inject bash functions into the bash completion script. Those bash functions are responsible for providing the completion choices for your own completions. Some code that works in kubernetes: -- cgit v1.2.3-54-g00ecf