Skip to content

Scale and Autoscale completion does not work as intended #1993

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

Open
hadasgayer opened this issue Mar 21, 2025 · 0 comments · May be fixed by #1994
Open

Scale and Autoscale completion does not work as intended #1993

hadasgayer opened this issue Mar 21, 2025 · 0 comments · May be fixed by #1994

Comments

@hadasgayer
Copy link

When running 'oc scale' or 'oc autoscale', tab completion only suggests the 'deploymentconfig' resource and not the rest of the relevant controllers. In addition, the completion does not find the relevant deploymentconfigs for scaling.

Impact

Completion is less helpful for scaling commands.

Expected Behavior

The initial completion should suggest deploymentconfig, deployment, replicaset, statefulset, or replicationcontroller. After completing the resource type, tab completion should suggest the relevant resources in the current or selected namespace.
In my opinion machinesets should be an option as well since they can be scaled with that command too when BMO is installed, but that's probably open to debate.

Steps to Reproduce

  1. Verify oc bash completion.
  2. Run 'oc scale' or 'oc autoscale' and press tab.
@hadasgayer hadasgayer linked a pull request Mar 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant