Hi @VinP
Unfortunately, directly removing Firestore from an Apigee Cloud Marketplace deployment after deployment isn't straightforward.
The Cloud Marketplace solutions are designed to be integrated with specific services, including Firestore in some cases. While you might be able to modify the deployed resources to some extent, completely removing a service like Firestore could lead to unexpected behavior or instability.
Here's a more nuanced approach to consider:
-
Evaluate the Specific Use Case:
- Clearly understand how Firestore is being used in your deployed solution.
- Determine if the functionality provided by Firestore is essential or if it can be replaced by CloudSQL or another suitable database.
-
Consult Apigee Support:
- Reach out to Apigee support for expert guidance on modifying the deployment.
- They can provide specific instructions and potential workarounds based on your use case.
-
Consider a New Deployment with Modified Configuration:
- If significant modifications are required, creating a new deployment with the desired configuration might be a more practical approach.
- This allows you to tailor the solution to your exact needs without affecting the existing deployment.
Potential Challenges and Considerations:
- Data Migration: If you're switching from Firestore to CloudSQL, you'll need to carefully migrate your data.
- Configuration Changes: Modifying the configuration of the deployed solution requires careful attention to avoid breaking the functionality.
- Security Implications: Any changes to the database configuration should be done with security in mind.
Remember: While it's possible to make modifications to a deployed Cloud Marketplace solution, it's crucial to approach the process with caution and seek expert advice when necessary.
I hope this provides a clearer understanding of the limitations and potential approaches.
Thanks!
LinkedIn
Twitter
