Add support for S3Key VersionID while publishing revision to CodeDeploy

Open
#102 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing where the plugin publishes a revision to AWS CodeDeploy and where the S3 bucket, key, and eTag are mapped into that request. Verify how VersionID should be accepted and passed for versioned buckets, while preserving current behavior when it is absent; done means the revision publication supports S3 object versions.

Written by the indexing model from the issue text.

Description

Currently we are publishing revision to CodeDeploy with S3Bucket+Key+eTag but we should add support VersionID as well for buckets with versioning enabled

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.