Skip to content

fix(configure): skip venv creation when --force and venv already exists#27

Merged
hailangvn merged 1 commit into
mainfrom
fix/configure-force-skip-venv
May 21, 2026
Merged

fix(configure): skip venv creation when --force and venv already exists#27
hailangvn merged 1 commit into
mainfrom
fix/configure-force-skip-venv

Conversation

@nilshamerlinck
Copy link
Copy Markdown
Contributor

Summary

  • --force now skips venv creation (for all types: odoo, python, package) when .venv already exists, consistent with how it skips git clone when the repo already exists
  • Adds _venv_exists helper and force parameter to setup_odoo_venv

Test plan

  • Run configure <instance> --force on an instance with an existing clone and venv — should skip both clone and venv creation with yellow warnings
  • Run configure <instance> (no --force) on a fresh instance — venv is created as before
  • Run configure <instance> (no --force) when instance already exists — should still error out

🤖 Generated with Claude Code

--force now ignores an existing clone AND an existing venv, consistent
with the skip-if-present approach used for git clone.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nilshamerlinck nilshamerlinck requested a review from hailangvn May 20, 2026 10:34
Copy link
Copy Markdown
Collaborator

@hailangvn hailangvn left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you.

@hailangvn hailangvn merged commit 8f04a1f into main May 21, 2026
5 checks passed
@hailangvn hailangvn deleted the fix/configure-force-skip-venv branch May 21, 2026 04:24
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 this pull request may close these issues.

2 participants