Global GCP discounts should not count in sandbox cost in DoIT
Dear DoIT, I've noticed a cost difference between the GCP billing and the Sandbox in CMP which would eventually affect the services running there when the default $100 limit is reached. The cost difference is due to using AlloyDB in the sandbox, w...
Currently it is not clear how the process of removing Sandboxes looks like: Your documentation https://help.doit-intl.com/cloud-sandbox-management/create-gcp-sandbox-accounts does not give information about how Sandboxes should be removed. Your su...
Close sandbox after a certain amount of time (Not just budget like today)
User wants to set a time-based limit to their sandboxes in situations where a budget limit is never reached.
The user would like sandboxes to self-destruct after a certain period of time — not necessarily when a budget threshold ...
Delete / grey out sandboxes in CMP when deleted from GCP
We have deleted the sandbox in their GCP and still see it as active in the CMP and it prevents us from creating more sandboxes unless changing the policy. Could we have a way to delete the sandbox from the CMP once it has been deleted from GCP as ...
This request is for security guardrails for sandbox projects. Meaning the ability to control what service(s) can/can't be accessed in sandbox projects created via CMP.
Right now you can set only budget guardrails for sandbox projects.
We have a prospect customer that considers creating a sandbox for each of his researchers staff. They have about 150 researches so it will be create if sandbox creation can be automated through CMP API.
User wants a flexible way to describe and deploy environments — Terraform is part of that flow and currently we don't support it.
This user wants to run Terraform as part of creating a sandbox.
This particular customer (email@example.com) is multi-cloud and thus requires sandbox environments for both GCP and AWS. Their current solution, env0, supports this. I'm sure other multi-cloud customers would appreciate such a feature as well.
As your cloud footprint grows, so do your costs. One way to minimize unnecessary cloud spend would be to shut off resources you're not using and to turn them back on when you use them again.
Doing this manually gets time-consuming as your company...