ecs-deploy | CLI tool to easily update your ECS services | AWS library

by travisjeffery Go Version: v1.3.0 License: No License

X-Ray Key Features Code Snippets(3)Community Discussions(8)Vulnerabilities Install Support

kandi X-RAY | ecs-deploy Summary

ecs-deploy is a Go library typically used in Cloud, AWS applications. ecs-deploy has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

CLI tool to easily update your ECS services.

Support

Quality

Security

License

Reuse

Support

ecs-deploy has a low active ecosystem.

It has 64 star(s) with 15 fork(s). There are 2 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 1 have been closed. On average issues are closed in 58 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ecs-deploy is v1.3.0

Quality

ecs-deploy has 0 bugs and 0 code smells.

Security

ecs-deploy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ecs-deploy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ecs-deploy does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

ecs-deploy releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed ecs-deploy and discovered the below as its top functions. This is intended to give you an instant insight into ecs-deploy implemented functionality, and help decide if they suit your requirements.

main is the main function
UpdateService updates a service
New returns a new ECS client

Get all kandi verified functions for this library.

ecs-deploy Key Features

No Key Features are available at this moment for ecs-deploy.

ecs-deploy Examples and Code Snippets

ecs-deploy,Usage

Lines of Code : 15

License : No License

Copy

usage: ecs-deploy --service=SERVICE []

Deploy ECS service.

Flags:
  --help                Show context-sensitive help (also try --help-long and --help-man).
  --service=SERVICE     Name of Service to update.
  --task=TASK-DEF       Name of Task Def

ecs-deploy,Example

Lines of Code : 5

License : No License

Copy

$ ecs-deploy --service=app --image=travisjeffery/app --tag=1.0.0
default/app-stage 2015/12/05 02:10:38 [info] --> desired: 2, pending: 0, running: 0
default/app-stage 2015/12/05 02:10:43 [info] --> desired: 1, pending: 1, running: 0
default/app

ecs-deploy,Install

Lines of Code : 1

License : No License

Copy

$ go get github.com/travisjeffery/ecs-deploy

Community Discussions

Trending Discussions on ecs-deploy

Pip wheel collects 2 versions of a package then pip install gets a conflict

GitHub Actions YAML for multiple deployment images for different stages with the same pipeline

GitHub Actions for multiple Environments

Authorization Error in Deploy AWS ECS Task Definition via Github Actions

How to use CodeDeploy with ECS, ALB and Auto Scaling

Why ECS pipeline needed Task Definition while Service already have the task definition assigned in AWS?

How to use previous task definition with ECS and bitbucket pipeline deployment

Jenkins ecs Command not found

QUESTION

Pip wheel collects 2 versions of a package then pip install gets a conflict

Asked 2022-Mar-16 at 08:19

We use a pipeline that first uses pip wheel to collect all the packages that are needed in the project and then it creates a docker image that calls to pip install on the collected wheels.

The issue I am encountering is that when calling pip wheel, pip is collecting 2 different versions of a package. This has started occurring once a new version of the package is available.

The project has a requirement for an internal library ecs-deployer==10.1.2 and that library has in turn a requirement in the form of: elb-listener>=3.2.1+25,<4

The relevant output of pip wheel with the verbose option says:

...

ANSWER

Answered 2022-Mar-09 at 22:16

As far as I understood, "local version identifiers" such as 3.2.1+25 are far from usual, apparently they are not meant to be used anywhere public (like PyPI), and that might be the reason for all the trouble here. I am really not sure how well they are supported by Python packaging tools and maybe they confuse the dependency resolution.

Local version identifiers SHOULD NOT be used when publishing upstream projects to a public index server, but MAY be used to identify private builds created directly from the project source. Local version identifiers SHOULD be used by downstream projects when releasing a version that is API compatible with the version of the upstream project identified by the public version identifier, but contains additional changes (such as bug fixes). As the Python Package Index is intended solely for indexing and hosting upstream projects, it MUST NOT allow the use of local version identifiers.

-- "Local version identifiers" section of _PEP 440

Source https://stackoverflow.com/questions/71416086

QUESTION

GitHub Actions YAML for multiple deployment images for different stages with the same pipeline

Asked 2021-Dec-31 at 02:03

I am working on a GitHub Actions Pipeline for the deployment of different images for a different environment, but I have been getting a "bad indentation of a mapping entry at line 72, column 5:" for this YAML, where I am trying to set prod variables, I have tried every which way but I am not sure what might be wrong here, please help me out.

...

ANSWER

Answered 2021-Dec-31 at 02:03

For what I checked here, the problem is on your setup job. You set 2 outputs fields for this job, with the same output names, but related to different steps (Set Vars and Set Prod Vars).

You can't have more than o e output field per job.

I separated them into 2 different jobs and it resolved the workflow error. You can check the final implementation here .

Note that I also updated the needs jobs for the subsequent jobs and outputs so it should work as expected.

Source https://stackoverflow.com/questions/70531237

QUESTION

GitHub Actions for multiple Environments

Asked 2021-Dec-23 at 02:57

I am working with GitHub to deploy a container based application on multiple environments, I have two environments,

Dev
Prod

I am building the application on both the Environments, this is my yml file:

...

ANSWER

Answered 2021-Dec-23 at 02:57

Until recent update aws actions required aws creds to be configured as github repo secret. After which it sets up as those creds in to env vars which makes them accessible in entire github action.

In your yml file it should be like this

Source https://stackoverflow.com/questions/70449167

QUESTION

Authorization Error in Deploy AWS ECS Task Definition via Github Actions

Asked 2021-Aug-24 at 15:47

I am trying to Deploy my image present in ECR using AWS ECS Fargate via Github Actions. It is a Github private repository as well as a private ECR repository. The AWS secrets are properly configured. I have also created an ecsTaskExecutionRole and included it in the Task Definition as per the AWS docs here. But the following error persists:

...

ANSWER

Answered 2021-Aug-21 at 13:34

There is a missing permission for the user user/service-account-ecr-push:

Source https://stackoverflow.com/questions/68873088

QUESTION

How to use CodeDeploy with ECS, ALB and Auto Scaling

Asked 2021-Feb-18 at 19:35

I'm trying to use CodeDeploy and ECS with an Application Load Balancer, and Auto Scaling with a strategy on the number of request of this ALB.

I'm using this URL as some sort of tutorial, but i don't really understand how CodeDeploy will integrate with ECS and other stuffs.

First, as i can see, i need two target groups on my ALB. But i only have one (that is, instance(s) that are / will be created by Auto Scaling)

So what do i need to do ? Does creating an empty target group, and telling CodeDeploy to use both work ?

What will it do, deploy instances in this target group and redirect a part of or the whole trafic to it once working ? As stated in the same link

"During deployment, CodeDeploy installs your update into a new, replacement task set."

So it seems to create new tasks, but on what instance then ?

...

ANSWER

Answered 2021-Feb-08 at 01:27

So what do i need to do ? Does creating an empty target group, and telling CodeDeploy to use both work ?

It can't be empty. Your new TG can be same as your first one. So at this stage you will have to TGs which are same (except thier name).

The second TG is specified when you create your ECS deployment group in CodeDeploy.

What will it do, deploy instances in this target group and redirect a part of or the whole traffic to it once working ? As stated in the same link

These will be same instances as the one running your current ecs task.

So it seems to create new tasks, but on what instance then ?

These will be same instances as those that run your current task.

Source https://stackoverflow.com/questions/66090487

QUESTION

Why ECS pipeline needed Task Definition while Service already have the task definition assigned in AWS?

Asked 2020-Sep-13 at 21:54

on bitbucket, the config is required to use both 'service' and 'task definition', I think this is redundant because the service already assigned with task definition, or we have an explanation?

...

ANSWER

Answered 2020-Sep-13 at 21:54

The task definition in ECS service you are showing is probably the initial deployment. When you do subsequent deployments you update the task definition with new image version, or extra parameters. You can't update ECS task without providing task definition.

The task definition is thus required. It's same if you use CodeDeploy to deploy to ECS - task definition must be provided:

-AppSpec 'resources' section for Amazon ECS deployments

TaskDefinition – Required. This is the task definition for the Amazon ECS service to deploy.

Source https://stackoverflow.com/questions/63874941

QUESTION

How to use previous task definition with ECS and bitbucket pipeline deployment

Asked 2020-May-19 at 05:04

I'm following this doc https://confluence.atlassian.com/bitbucket/deploy-to-amazon-ecs-892623902.html to set up a pipeline to deploy to the ECS cluster.

This doc is using a custom task def JSON file and using the same for the deployment after updating the image name.

Am I required to copy the complete task definition JSON and put that in my repository? My task definition has lots of environment variables in it. I do not want to expose them by putting it in the repository.

Or, the task definition template will update the default task definition and create a new revision. (not overwrite)

The deployment step is

...

ANSWER

Answered 2020-May-18 at 22:01

You can use aws cli to run this command and retrieve the existing task definition JSON: https://docs.aws.amazon.com/cli/latest/reference/ecs/describe-task-definition.html

Source https://stackoverflow.com/questions/61870907

QUESTION

Jenkins ecs Command not found

Asked 2020-Feb-06 at 19:00

I installed third party tool (ecs deploy using pip install ecs-deploy) .When I try to deploy using command ecs deploy demo-cluster demo-service in command prompt its working fine when I try with jenkins to deploy getting error

...

ANSWER

Answered 2020-Feb-05 at 12:24

You need to run the full AWS CLI command:

Source https://stackoverflow.com/questions/60044044

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ecs-deploy

Download the binary, or go get:.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: