Missing Option to overwrite in case there are files in destination (--file-exists-behavior)

Open
#83 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, java
Domain
cloud, devops

Research direction

No files, tests, or entry points are identified in the issue. Start by locating the handling for deployment options and the AWS CodeDeploy invocation; done means users can select the requested file-exists behavior instead of deployment failing when a destination file already exists.

Written by the indexing model from the issue text.

Description

enhancement

It would be great if you add the option to set the --file-exists-behavior so that we can choose what do do in case a file exists.

Right now if a file exists the deploy just fails.

Dominant language
Java
Stars
156
Forks
130
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-codedeploy-plugin

All issues in awslabs/aws-codedeploy-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.