odoo-devops-tools 1.23.1__tar.gz → 1.23.2__tar.gz

{odoo_devops_tools-1.23.1 → odoo_devops_tools-1.23.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: odoo-devops-tools
-Version: 1.23.1
+Version: 1.23.2
 Summary: Build reproducible Odoo workspaces from a single project definition.
 Author: Roman Lacko
 License-Expression: MIT
@@ -120,7 +120,7 @@ Choose the workflow that fits your environment. Both use the same `odoo-project.
 Create a new workspace:
 
 ```bash
-odoo-compose --init-project ./odoo19
+odoo-compose --init ./odoo19
 ```
 
 Start the Docker Compose environment:
@@ -514,7 +514,7 @@ In this workflow, Odoo runs directly on the host using a generated Python virtua
 Create the workspace with the Odoo source and virtual environment:
 
 ```bash
-odoo-compose --init-project ./odoo19 --sync-all --create-venv \
+odoo-compose --init ./odoo19 --sync-all --create-venv \
   --set config:db_host=127.0.0.1 \
   --set config:db_name=odoo \
   --set config:db_user=odoo \
@@ -952,7 +952,7 @@ The merged project file is saved as `ROOT/odoo-project.ini`, replacing any exist
 ### Paths and outputs
 
 - `--root ROOT` — workspace root directory. Default: the directory containing a local INI file, or the current working directory for a remote INI or omitted INI. In include mode, the default is the directory of the first local source, or the current working directory when the first source is remote.
-- `--init-project [ROOT]` — create `ROOT/odoo-project.ini` from the bundled default template if it does not already exist. `ROOT` is optional; when supplied, it is a shorthand for selecting the workspace root directly, for example `odoo-compose --init-project ./odoo19`. When the optional value is omitted, `--root ROOT` remains supported for backward compatibility. Do not supply both `--init-project ROOT` and `--root ROOT`; the command exits with an error instead of choosing one implicitly. This option is valid only when `INI` is omitted and no `-i/--include` is provided. Existing project files are not overwritten.
+- `--init [ROOT]` — create `ROOT/odoo-project.ini` from the bundled default template if it does not already exist. `ROOT` is optional; when supplied, it is a shorthand for selecting the workspace root directly, for example `odoo-compose --init ./odoo19`. When the optional value is omitted, `--root ROOT` remains supported for backward compatibility. Do not supply both `--init ROOT` and `--root ROOT`; the command exits with an error instead of choosing one implicitly. This option is valid only when `INI` is omitted and no `-i/--include` is provided. Existing project files are not overwritten.
 - `--include INI`, `-i INI` — include an additional project INI layer; can be repeated. Later layers override earlier layers.
 - `--extra-var KEY=VALUE`, `-e KEY=VALUE` — override or inject a value in the optional `[vars]` section; can be repeated.
 - `--set SECTION:KEY=VALUE`, `-S SECTION:KEY=VALUE` — set or override a supported project option; can be repeated. Missing supported sections/options are created automatically. Structured sections (`[virtualenv]`, `[odoo]`, `[addons.<name>]`, and `[docker]`) accept only documented keys; `[config]` remains open to standard Odoo configuration options except `addons_path`.
@@ -1023,7 +1023,7 @@ The following sections are supported:
 
 ### General rules
 
-- The project file can have any filename when passed explicitly. When `INI` is omitted, `odoo-compose` uses the existing `ROOT/odoo-project.ini`; if it is missing, use `--init-project` to create it explicitly from the bundled default template. Remote INI sources and merged include layers are materialized as `ROOT/odoo-project.ini`.
+- The project file can have any filename when passed explicitly. When `INI` is omitted, `odoo-compose` uses the existing `ROOT/odoo-project.ini`; if it is missing, use `--init` to create it explicitly from the bundled default template. Remote INI sources and merged include layers are materialized as `ROOT/odoo-project.ini`.
 - INI interpolation is supported, so values such as `${odoo:version}` can be reused across sections.
 - Multiple INI layers can be composed with `-i/--include`. Later layers override earlier layers; multi-line values are replaced as whole option values, not appended.
 - The optional `[vars]` section is useful for reusable values referenced as `${vars:name}`.

{odoo_devops_tools-1.23.1 → odoo_devops_tools-1.23.2}/README.md

@@ -92,7 +92,7 @@ Choose the workflow that fits your environment. Both use the same `odoo-project.
 Create a new workspace:
 
 ```bash
-odoo-compose --init-project ./odoo19
+odoo-compose --init ./odoo19
 ```
 
 Start the Docker Compose environment:
@@ -486,7 +486,7 @@ In this workflow, Odoo runs directly on the host using a generated Python virtua
 Create the workspace with the Odoo source and virtual environment:
 
 ```bash
-odoo-compose --init-project ./odoo19 --sync-all --create-venv \
+odoo-compose --init ./odoo19 --sync-all --create-venv \
   --set config:db_host=127.0.0.1 \
   --set config:db_name=odoo \
   --set config:db_user=odoo \
@@ -924,7 +924,7 @@ The merged project file is saved as `ROOT/odoo-project.ini`, replacing any exist
 ### Paths and outputs
 
 - `--root ROOT` — workspace root directory. Default: the directory containing a local INI file, or the current working directory for a remote INI or omitted INI. In include mode, the default is the directory of the first local source, or the current working directory when the first source is remote.
-- `--init-project [ROOT]` — create `ROOT/odoo-project.ini` from the bundled default template if it does not already exist. `ROOT` is optional; when supplied, it is a shorthand for selecting the workspace root directly, for example `odoo-compose --init-project ./odoo19`. When the optional value is omitted, `--root ROOT` remains supported for backward compatibility. Do not supply both `--init-project ROOT` and `--root ROOT`; the command exits with an error instead of choosing one implicitly. This option is valid only when `INI` is omitted and no `-i/--include` is provided. Existing project files are not overwritten.
+- `--init [ROOT]` — create `ROOT/odoo-project.ini` from the bundled default template if it does not already exist. `ROOT` is optional; when supplied, it is a shorthand for selecting the workspace root directly, for example `odoo-compose --init ./odoo19`. When the optional value is omitted, `--root ROOT` remains supported for backward compatibility. Do not supply both `--init ROOT` and `--root ROOT`; the command exits with an error instead of choosing one implicitly. This option is valid only when `INI` is omitted and no `-i/--include` is provided. Existing project files are not overwritten.
 - `--include INI`, `-i INI` — include an additional project INI layer; can be repeated. Later layers override earlier layers.
 - `--extra-var KEY=VALUE`, `-e KEY=VALUE` — override or inject a value in the optional `[vars]` section; can be repeated.
 - `--set SECTION:KEY=VALUE`, `-S SECTION:KEY=VALUE` — set or override a supported project option; can be repeated. Missing supported sections/options are created automatically. Structured sections (`[virtualenv]`, `[odoo]`, `[addons.<name>]`, and `[docker]`) accept only documented keys; `[config]` remains open to standard Odoo configuration options except `addons_path`.
@@ -995,7 +995,7 @@ The following sections are supported:
 
 ### General rules
 
-- The project file can have any filename when passed explicitly. When `INI` is omitted, `odoo-compose` uses the existing `ROOT/odoo-project.ini`; if it is missing, use `--init-project` to create it explicitly from the bundled default template. Remote INI sources and merged include layers are materialized as `ROOT/odoo-project.ini`.
+- The project file can have any filename when passed explicitly. When `INI` is omitted, `odoo-compose` uses the existing `ROOT/odoo-project.ini`; if it is missing, use `--init` to create it explicitly from the bundled default template. Remote INI sources and merged include layers are materialized as `ROOT/odoo-project.ini`.
 - INI interpolation is supported, so values such as `${odoo:version}` can be reused across sections.
 - Multiple INI layers can be composed with `-i/--include`. Later layers override earlier layers; multi-line values are replaced as whole option values, not appended.
 - The optional `[vars]` section is useful for reusable values referenced as `${vars:name}`.

odoo_devops_tools-1.23.2/odoo_devops_tools/__init__.py

@@ -0,0 +1 @@
+__version__ = "1.23.2"

{odoo_devops_tools-1.23.1 → odoo_devops_tools-1.23.2}/odoo_devops_tools/env.py

@@ -6247,11 +6247,11 @@ def build_parser() -> argparse.ArgumentParser:
 Examples:
 
   Creating a workspace:
-    odoo-compose --init-project ./odoo18-workspace --sync-all --create-venv \\
+    odoo-compose --init ./odoo18-workspace --sync-all --create-venv \\
       --set odoo:version=18.0
 
   Creating a workspace with explicit database settings:
-    odoo-compose --init-project ./odoo18-workspace --sync-all --create-venv \\
+    odoo-compose --init ./odoo18-workspace --sync-all --create-venv \\
       --set odoo:version=18.0 \\
       --set config:db_host=127.0.0.1 \\
       --set config:db_name=odoo \\
@@ -6268,7 +6268,7 @@ Examples:
     odoo-compose git+https://github.com/lck/odoo-devops-tools.git//examples/odoo18-minimal.ini?ref=main --sync-all --create-venv
 
   Preparing local Docker development:
-    odoo-compose --init-project ./odoo19 --sync-addons
+    odoo-compose --init ./odoo19 --sync-addons
 
   Generating a deploy Docker build context:
     odoo-compose /path/to/odoo-project.ini --sync-addons --create-docker-deploy
@@ -6336,7 +6336,9 @@ Examples:
     )
 
     parser.add_argument(
+        "--init",
         "--init-project",
+        dest="init_project",
         nargs="?",
         const="",
         default=None,
@@ -6345,7 +6347,7 @@ Examples:
             "Create ROOT/odoo-project.ini from the bundled default template if it does not already exist. "
             "An optional ROOT can be supplied directly as shorthand for --root. "
             "If ROOT is supplied here, --root must not also be used. "
-            "Without --init-project, an existing ROOT/odoo-project.ini is required."
+            "Without --init, an existing ROOT/odoo-project.ini is required."
         ),
     )
 
@@ -6592,12 +6594,12 @@ def main() -> None:
 
     if init_project_root_raw and args.root:
         parser.error(
-            "workspace ROOT was specified both as --init-project ROOT and --root; "
+            "workspace ROOT was specified both as --init ROOT and --root; "
             "use only one of them."
         )
 
     if bool(getattr(args, 'show_last_run', False)) and init_project:
-        parser.error("--init-project cannot be used together with --show-last-run.")
+        parser.error("--init cannot be used together with --show-last-run.")
     if bool(getattr(args, 'show_last_run', False)) and getattr(args, 'create_from_bundle', None):
         parser.error("--create-from-bundle cannot be used together with --show-last-run.")
     if bool(getattr(args, 'show_last_run', False)) and getattr(args, 'create_bundle', None) is not None:
@@ -6656,7 +6658,7 @@ def main() -> None:
         if getattr(args, 'include_inis', None):
             conflicting_options.append("--include")
         if init_project:
-            conflicting_options.append("--init-project")
+            conflicting_options.append("--init")
         if args.all or args.odoo or args.addons:
             conflicting_options.append("--sync-*")
         if bool(getattr(args, 'create_venv', False)) or create_venv_from_wheelhouse:
@@ -6737,14 +6739,14 @@ def main() -> None:
     project_ini_status: Optional[str] = None
 
     if init_project and not implicit_ini:
-        parser.error("--init-project can only be used when INI is omitted and no -i/--include is provided.")
+        parser.error("--init can only be used when INI is omitted and no -i/--include is provided.")
 
     if implicit_ini:
         if init_project_root_raw:
             root_override = _validate_root_override(
                 parser,
                 init_project_root_raw,
-                option_name="--init-project ROOT",
+                option_name="--init ROOT",
             )
         elif args.root:
             root_override = _validate_root_override(parser, args.root)
@@ -6781,7 +6783,7 @@ def main() -> None:
                     project_ini_status = f"used existing ROOT/{_DEFAULT_PROJECT_INI_NAME}"
                     _logger.info("Project INI already exists, leaving it in place: %s", ini_path)
             elif not ini_path.is_file():
-                suggested_cmd = ["odoo-compose", "--init-project"]
+                suggested_cmd = ["odoo-compose", "--init"]
                 if args.root:
                     suggested_cmd.append(str(root_override))
                 parser.error(

{odoo_devops_tools-1.23.1 → odoo_devops_tools-1.23.2}/odoo_devops_tools.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: odoo-devops-tools
-Version: 1.23.1
+Version: 1.23.2
 Summary: Build reproducible Odoo workspaces from a single project definition.
 Author: Roman Lacko
 License-Expression: MIT
@@ -120,7 +120,7 @@ Choose the workflow that fits your environment. Both use the same `odoo-project.
 Create a new workspace:
 
 ```bash
-odoo-compose --init-project ./odoo19
+odoo-compose --init ./odoo19
 ```
 
 Start the Docker Compose environment:
@@ -514,7 +514,7 @@ In this workflow, Odoo runs directly on the host using a generated Python virtua
 Create the workspace with the Odoo source and virtual environment:
 
 ```bash
-odoo-compose --init-project ./odoo19 --sync-all --create-venv \
+odoo-compose --init ./odoo19 --sync-all --create-venv \
   --set config:db_host=127.0.0.1 \
   --set config:db_name=odoo \
   --set config:db_user=odoo \
@@ -952,7 +952,7 @@ The merged project file is saved as `ROOT/odoo-project.ini`, replacing any exist
 ### Paths and outputs
 
 - `--root ROOT` — workspace root directory. Default: the directory containing a local INI file, or the current working directory for a remote INI or omitted INI. In include mode, the default is the directory of the first local source, or the current working directory when the first source is remote.
-- `--init-project [ROOT]` — create `ROOT/odoo-project.ini` from the bundled default template if it does not already exist. `ROOT` is optional; when supplied, it is a shorthand for selecting the workspace root directly, for example `odoo-compose --init-project ./odoo19`. When the optional value is omitted, `--root ROOT` remains supported for backward compatibility. Do not supply both `--init-project ROOT` and `--root ROOT`; the command exits with an error instead of choosing one implicitly. This option is valid only when `INI` is omitted and no `-i/--include` is provided. Existing project files are not overwritten.
+- `--init [ROOT]` — create `ROOT/odoo-project.ini` from the bundled default template if it does not already exist. `ROOT` is optional; when supplied, it is a shorthand for selecting the workspace root directly, for example `odoo-compose --init ./odoo19`. When the optional value is omitted, `--root ROOT` remains supported for backward compatibility. Do not supply both `--init ROOT` and `--root ROOT`; the command exits with an error instead of choosing one implicitly. This option is valid only when `INI` is omitted and no `-i/--include` is provided. Existing project files are not overwritten.
 - `--include INI`, `-i INI` — include an additional project INI layer; can be repeated. Later layers override earlier layers.
 - `--extra-var KEY=VALUE`, `-e KEY=VALUE` — override or inject a value in the optional `[vars]` section; can be repeated.
 - `--set SECTION:KEY=VALUE`, `-S SECTION:KEY=VALUE` — set or override a supported project option; can be repeated. Missing supported sections/options are created automatically. Structured sections (`[virtualenv]`, `[odoo]`, `[addons.<name>]`, and `[docker]`) accept only documented keys; `[config]` remains open to standard Odoo configuration options except `addons_path`.
@@ -1023,7 +1023,7 @@ The following sections are supported:
 
 ### General rules
 
-- The project file can have any filename when passed explicitly. When `INI` is omitted, `odoo-compose` uses the existing `ROOT/odoo-project.ini`; if it is missing, use `--init-project` to create it explicitly from the bundled default template. Remote INI sources and merged include layers are materialized as `ROOT/odoo-project.ini`.
+- The project file can have any filename when passed explicitly. When `INI` is omitted, `odoo-compose` uses the existing `ROOT/odoo-project.ini`; if it is missing, use `--init` to create it explicitly from the bundled default template. Remote INI sources and merged include layers are materialized as `ROOT/odoo-project.ini`.
 - INI interpolation is supported, so values such as `${odoo:version}` can be reused across sections.
 - Multiple INI layers can be composed with `-i/--include`. Later layers override earlier layers; multi-line values are replaced as whole option values, not appended.
 - The optional `[vars]` section is useful for reusable values referenced as `${vars:name}`.

{odoo_devops_tools-1.23.1 → odoo_devops_tools-1.23.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "odoo-devops-tools"
-version = "1.23.1"
+version = "1.23.2"
 description = "Build reproducible Odoo workspaces from a single project definition."
 readme = "README.md"
 license = "MIT"

odoo_devops_tools-1.23.1/odoo_devops_tools/__init__.py

@@ -1 +0,0 @@
-__version__ = "1.23.1"