You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement Fargate and Local distributors as part of Cloud Deployer
Expected Behavior
CLI should read terraform.distributor value and provision terrahub component in corresponding service. The config would look like this:
project:
name: my_projectdistributor: fargate # default: local; all options: local|lambda|fargate|appEngine|cloudFunctions[...]
or
component:
name: my_componentdistributor: fargate # default: local; all options: local|lambda|fargate|appEngine|cloudFunctions[...]
When fargate is specified, corresponding terrahub component should be launched in Amazon ECS using Fargate task type. This means that Docker image used in ECS should be predefined and stored in Amazon ECR.
The text was updated successfully, but these errors were encountered:
Additionally, let's add distributor: local value, which will allow to use local environment for specific terrahub component. In summary, allowed values will be local, lambda (default), fargate, appEngine and cloudFunctions.
eistrati
changed the title
Add Fargate distributor as part of Cloud Deployer
Implement Fargate and Local distributors as part of Cloud Deployer
Sep 9, 2019
Describe the Feature
Implement Fargate and Local distributors as part of Cloud Deployer
Expected Behavior
CLI should read
terraform.distributor
value and provision terrahub component in corresponding service. The config would look like this:or
When
fargate
is specified, corresponding terrahub component should be launched in Amazon ECS using Fargate task type. This means that Docker image used in ECS should be predefined and stored in Amazon ECR.The text was updated successfully, but these errors were encountered: