Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[CLI] operator update should be suggested only if an installation is detected

Open
#41 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start at the CLI entry point for ops -update and trace the check that reports a newer operator version. Reproduce the command with and without an active operator installation. Done means the update suggestion appears only when an active installation is detected.

Written by the indexing model from the issue text.

Description

bug

Updating the ops cli using 'ops -update` always reports that a newer version of the operator is available and that it can be updated using a specific tasks, e.g.

`Welcome to ops! Setting up...
Cloning tasks...
Enumerating objects: 3661, done.
Counting objects: 100% (289/289), done.
Compressing objects: 100% (110/110), done.
Total 3661 (delta 164), reused 271 (delta 158), pack-reused 3372
Tasks downloaded successfully

New operator version detected!
Current deployed operator can be updated with: ops update operator`

We should change the behaviour to trigger this check only if an active installation is detected

Dominant language
Python
Stars
576
Forks
29
Avg merge
51m
Merged PRs (30d)
14

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/openserverless

All issues in apache/openserverless

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.