| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 65 |
| Technical Name |
ganemo_devops_access |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 65 |
| Technical Name |
ganemo_devops_access |
| License | OPL-1 |
| Website | https://www.ganemo.co |
DevOps Access
Autonomous Bot & API Key Provisioning
Automatically creates a dedicated DevOps bot user with a generated API key in Odoo 19, enabling the Antigravity AI agent to autonomously inspect deployment logs after an Odoo.SH build failure — without manual intervention.
What We're Solving
----------------
Manual Log Inspection Bottleneck
After a failed Odoo.SH deployment, inspecting ir.logging for root-cause errors typically requires a human developer to log in manually. This module eliminates that bottleneck by provisioning a dedicated bot user with API access automatically at install time.
Secure API Key Management
API keys are generated programmatically via Odoo's native ir.api.key model and stored securely in ir.config_parameter. No hardcoded credentials, no manual key management. The key is accessible only to the DevOps agent via JSON-RPC 2.0.
Setup & How It Works
Zero-Configuration Automation
1. Automatic Provisioning on Install
What happens automatically when the module is installed:
- A bot user agent@ganemo.co is created (or reused if existing).
- The user is assigned to the ERP Manager group (
base.group_erp_manager).
- A new Odoo API Key is generated and stored in
ir.config_parameterunderganemo_devops.api_key. - On uninstall, the bot user and the config parameter are automatically removed.
ir.logging entries after a
deployment failure.
2. Agent Workflow After Deployment
What the Antigravity agent does with this module installed:
Deploy to Odoo.SH
The agent pushes the module set to the designated Odoo.SH branch and waits for the build to complete.
Retrieve API Key
The agent reads ganemo_devops.api_key
from ir.config_parameter via JSON-RPC using
the bot user credentials.
Inspect ir.logging
The agent queries ir.logging for
ERROR-level entries, extracting tracebacks and
root causes without any human in the loop.
Auto-Fix & Retry
Using the extracted error information, the agent applies targeted code fixes and re-deploys automatically, closing the DevOps feedback loop.
Global Ready | Multi-Language Support
This module is fully translated into English and Spanish (en_US, es_ES, es_PE, es_MX), ensuring a professional experience for international organizations.
Why Choose Ganemo?
----------------
Ganemo is the world's leading Odoo App developer and a multi-award-winning Gold Partner. For over 5 years, we have been recognized as the #1 seller of high-quality apps on the Odoo App Store. Trusted as the "Best Partner" in USA, Mexico, Chile, Spain, Colombia, Ecuador, and Peru, we deliver robust, secure, and localization-compliant solutions for global businesses.
Get a Quote & Resolve Commercial Doubts
Join thousands of satisfied clients on Odoo. Contact our sales team directly.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Schedule Meeting
Need More? We Do It All
Professional Odoo Services
ERP Implementation
Transform your business with a full Odoo implementation. We analyze, configure, and train your team to maximize productivity. From Accounting to Inventory, we handle the complexity so you can focus on growth.
Module Dev & Migration
Need a custom feature? Or stuck on an older version? We develop high-performance custom modules and migrate your existing code to Odoo 19 with zero data loss. Expert developers at your service.
QA / User Testing Scenarios
Enterprise Validation Plan
Scenario 1: Bot User Auto-Provisioning
- Install the module ganemo_devops_access on a staging Odoo.SH instance.
- Go to Settings > Users.
- Expected: A user
agent@ganemo.co(Ganemo DevOps Bot) is present and active. - Expected: The user belongs to the ERP Manager group.
Scenario 2: API Key Generation & Storage
- After installation, go to Settings > Technical > Parameters > System Parameters.
- Search for
ganemo_devops.api_key. - Expected: The parameter exists with a non-empty API key value.
- Authenticate via JSON-RPC 2.0 using the bot user and the API key. Read
ir.logging. - Expected: Authentication succeeds and log records are returned.
Scenario 3: Clean Uninstall
- Uninstall ganemo_devops_access.
- Expected: The bot user
agent@ganemo.cois removed (or archived). - Expected: The
ganemo_devops.api_keysystem parameter is deleted. - Expected: No orphaned API keys remain in
ir.api.key.
FAQ & Troubleshooting
Common Resolutions
Bot user was not created after install?
Reason: The post_init_hook may have failed silently due to a missing Enterprise module dependency (ir.api.key).
Fix: Ensure you are installing on an Odoo 19 Enterprise environment (not Community). Check ir.logging for post_init_hook errors.
Can I install this on production?
Answer: This module is designed for staging/testing environments only.
Warning: Installing on production grants the bot user ERP Manager access. Only install if you fully understand the security implications.
API key is empty or authentication fails?
Reason: The key may not have been generated correctly during the hook.
Fix: Uninstall and reinstall the module. The uninstall_hook will clean up, and a fresh post_init_hook will regenerate the key.
Is this compatible with multi-company?
Answer: The bot user is a standard Odoo user with global access. It operates at the ERP Manager level, independent of company context.
Detail: The bot user can read ir.logging across all companies in the database.
Commercial & Sales
For inquiries about licenses, demos, or partnerships.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Technical Support
Existing customers regarding module functionality.
Help Desk
Exclusive channel for technical assistance and bug reports.
help@ganemo.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module