GCP configuration LANCER

Lancer : Ideal for quick, focused engagements Team: ≤ 2 resources Duration: ≤ 3 weeks Indicative Budget: ≤ $3,000 USD* Use Cases: MVPs, prototypes, simple websites, bug-fix sprints Indicative Pricing: ~$15–$25/hr per resource*

Growth : Best suited for growing products or structured builds Team: 2–5 resources Duration: Up to 4 months Indicative Budget: Up to $30,000 USD* Use Cases: Feature-rich web apps, integrations, custom dashboards Indicative Pricing: ~$15–$35/hr per resource*

Enterprise : Tailored for high-scale, complex or long-term initiatives Team: 5+ resources Duration: More than 4 months Indicative Budget: Starts from $30,000+ USD* Use Cases: End-to-end platforms, SaaS products, compliance-heavy systems Indicative Pricing: ~$25–$50/hr depending on roles*

(Development)

Technologies Involved:

API INTEGRATIONS

Project Description

Oodles was engaged to improve deployment logic for a Google Cloud Platform (GCP) environment by implementing a configuration-based flag system. The objective was to provide users with a choice to either clean the existing GCP setup or reuse it, but only if the existing setup matched the defined configuration parameters. The feature aimed to safeguard against unauthorized resets and misaligned infrastructure setups.

Scope Of Work

The client required enhancements to the main.py script to introduce a user-controlled flag (1 or 0) for managing GCP deployments. If the flag was set to 1, the system would clean the current setup; if set to 0, it had to validate the current infrastructure against the values in a local config.json file (such as number of nodes) before proceeding. In case of mismatches, a clear error message had to be shown to prevent unintended overwrites. The solution needed to integrate seamlessly with the existing deploy-sut.sh script and GCP APIs.

Our Solution

To meet the client’s configuration control needs, Oodles delivered:

Enhanced main.py with a binary flag (1/0) for deployment logic control
Integrated logic to trigger deploy-sut.sh for cleaning GCP setup when flag = 1
Built a validation routine to compare config.json with actual GCP state via API
Added logic to detect mismatches in node count or key parameters
Implemented precise error messages and halted deployment on mismatch detection
Ensured clean fallback behavior and prevented unauthorized setup changes
Delivered code with inline documentation and testing support for further extensions

Project Description

Scope Of Work

Our Solution

Related Projects