- Introduce `staging-reset-job.yaml` template to handle staging database reset via Kubernetes Job
- Remove `staging.reset` value from `values.yaml` and `test_values/odoo.knd.local.yaml`
- Update `deploy-staging.yaml` to remove reset logic and retain only enterprise addon cloning
- Add `unsuspend-job` and `suspend-job` task commands to manage job execution
- Update README.md to document the new suspended job and how to trigger it
- Ensure `task test-odoo-chart` waits for Odoo deployment before proceeding
- Add `aggregate-git-repos` step to `deploy.yaml` for consistency with staging deployment
- Update image tag in Backup.md to mintsystem/odoo:18.0.20251222
- Update image tag in Development.md task example to mintsystem/odoo:18.0.20251222
- Update image tag in test_values/odoo.knd.local.yaml to mintsystem/odoo:18.0.20251222
- Comment out GitLab third-party addons repository in `odoo.knd.local.yaml` to avoid unnecessary cloning in local environments
- Keep `staging.reset: false` to maintain production-like behavior in local setups
- Bump Odoo image from `18.0.20251106` to `18.0.20251121` across documentation and test values
- Add support for GitLab credentials in `odoo-creds` secret for private repository access
- Introduce `staging.reset` parameter to control database cloning and neutralization on container init
- Update staging deployment template to conditionally execute database reset logic
- Add GitLab repository to test values for third-party addons
- Set `staging.reset` to `false` in `odoo.knd.local.yaml` to disable automatic reset in production-like environments
- Bump Odoo image from `18.0.20251008` to `18.0.20251106` across documentation and test values
- Update OCA and Mint-System repository branches from `16.0` to `18.0` in test values to match Odoo 18.0 compatibility
- Adjust Development.md and Backup.md to reflect the new image tag for local development and backup procedures
- Introduce `additionalEnvs` parameter to allow setting custom environment variables in the taskfileBuild chart
- Update ConfigMap template to include additional environment variables
- Add example usage in test-values.yaml
- Update README.md with documentation for the new `additionalEnvs` parameter
- Rename test directories from `test/` to `test_values/` for clarity
- Update documentation and task scripts to reflect the new directory structure
Janik von Rotz