Dev
Dev
Currently the default tier type used when provisioning Google Cloud SQL instance is db-n1-standard-1. This should be made configurable in the environment definition.
Currently CloudARK supports 'mysql' as the engine type when creating RDS instances. Add support for other engine types.
Currently the logic of binding is based on using the 'type' of the resource defined in an environment. https://cloud-ark.github.io/cloudark/docs/html/html/env_vars.html However, this approach will break if the environment definition contains two...
When application container is stored in GCR, it is not getting deleted through 'cld container delete'. In the code we have implemented appropriate calls https://github.com/cloud-ark/cloudark/blob/master/server/server_plugins/gcloud/resource/gcr.py#L71 However, this is failing. So...
When CloudARK deploys an application in an environment, there is opportunity for perform several pre-deployment checks that can catch deployment related issues early. Some such checks include: - Whether requested...
We should make sure that environment names and application names adhere to naming constraints defined by the underlying cloud. For instance, AWS RDS's name needs to be according to following...
We need validation for the environment definition. This should include verifying that the env yaml contains all the required fields, their values are satisfying appropriate constraints, etc.
CloudARK should support an easy way to locally run multi-container applications. The main constraint is that the "local coe" backend should behaviorally be similar to the eventual target of deployment....
We are using thread module to create worker threads. This module is available in 2.7.* versions of Python but not in 3.* versions. a) In the short term -- check...
Currently CloudARK supports building and pushing containers to Amazon's container registry (ECR) and Google's container registry (GCR). We should add support for Public or Private repositories in Docker Hub registry...