Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Fargate and Local distributors as part of Cloud Deployer #866

Open
eistrati opened this issue Sep 3, 2019 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@eistrati
Copy link
Contributor

eistrati commented Sep 3, 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:

project:
  name: my_project
  distributor: fargate   # default: local; all options: local|lambda|fargate|appEngine|cloudFunctions
  [...]

or

component:
  name: my_component
  distributor: 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.

@eistrati eistrati added the enhancement New feature or request label Sep 3, 2019
@eistrati
Copy link
Contributor Author

eistrati commented Sep 4, 2019

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 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
@igorbeiu igorbeiu assigned igorbeiu and unassigned aluchianic Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants