aws s3 sync --existing - Githubissues

ChrisSLT commented 9 years ago

Could you implement a feature like RYNC's --existing so that you can tell AWS to "skip creating files that do not exist yet on the destination"

Or is there a way to do this already?

The use case is you have just synced from machine 1 up to S3 and you have a huge dataset in S3. Now you want to sync down from S3 to machine 2 so you're working with up to date files on machine 2. But you only want to update files that are already on machine 2, you don't want to copy the huge dataset in S3 down.

Make sense?

jamesls commented 9 years ago

Not currently possible to do with the CLI. The closest thing you could is either:

a) only sync up to a specific prefix (s3://bucket/specific/dataset/) b) only sync with --exclude/--include filters: `--exclude '' --include '.txt' s3://bucket/specific/prefix)

This could end up being a little tricky to implement efficiently, we may have to switch our internals to use HeadObject instead of ListObjects if --existing is specified.

Marking as a feature request.

ASayre commented 6 years ago

Good Morning!

We're closing this issue here on GitHub, as part of our migration to UserVoice for feature requests involving the AWS CLI.

This will let us get the most important features to you, by making it easier to search for and show support for the features you care the most about, without diluting the conversation with bug reports.

As a quick UserVoice primer (if not already familiar): after an idea is posted, people can vote on the ideas, and the product team will be responding directly to the most popular suggestions.

We’ve imported existing feature requests from GitHub - Search for this issue there!

And don't worry, this issue will still exist on GitHub for posterity's sake. As it’s a text-only import of the original post into UserVoice, we’ll still be keeping in mind the comments and discussion that already exist here on the GitHub issue.

GitHub will remain the channel for reporting bugs.

Once again, this issue can now be found by searching for the title on: https://aws.uservoice.com/forums/598381-aws-command-line-interface

-The AWS SDKs & Tools Team

salmanwaheed commented 6 years ago

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred:

mkdirenv@gmail.com Domain salmanwaheed.info has exceeded the max emails per hour (151/150 (100%)) allowed. Message will be reattempted later

------- This is a copy of the message, including all the headers. ------ Received: from o6.sgmail.github.com ([192.254.113.101]:15527) by box1177.bluehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from bounces+848413-a7b0-hello=salmanwaheed.info@sgmail.github.com) id 1ej0P0-001aQr-2u for hello@salmanwaheed.info; Tue, 06 Feb 2018 03:23:02 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=/t1gsJYfR73hQ6vvFLB/iP0xSyA=; b=vKaTxQ8wPjZacKM+ IKAnxNMMZtwGHxRP92zsIRP0khdOIJalNYPOzUXK+KMLL7UNQDPRqQNX8Hbuomet OtikFHIuPyqhgm491tM62NzuF70mA96eloeARt3FSVCSRyjtEM4bLaM/0Yp77L4G RuSJYt3EF2ITYHYK3JAaeVd29Uo= Received: by filter0965p1mdw1.sendgrid.net with SMTP id filter0965p1mdw1-12325-5A7981DE-6 2018-02-06 10:22:22.177225152 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 5tkgWZitTmmnQjYUx5_V8A for hello@salmanwaheed.info; Tue, 06 Feb 2018 10:22:22.174 +0000 (UTC) Date: Tue, 06 Feb 2018 10:22:22 +0000 (UTC) From: Andre Sayre notifications@github.com Reply-To: aws/aws-cli reply@reply.github.com To: aws/aws-cli aws-cli@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Message-ID: aws/aws-cli/issue/1449/issue_event/1459787911@github.com In-Reply-To: aws/aws-cli/issues/1449@github.com References: aws/aws-cli/issues/1449@github.com Subject: Re: [aws/aws-cli] aws s3 sync --existing (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a7981dd3ccbd_8363fbb60110f3476784"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ASayre X-GitHub-Recipient: salmanwaheed X-GitHub-Reason: subscribed List-ID: aws/aws-cli List-Archive: https://github.com/aws/aws-cli List-Post: mailto:reply@reply.github.com List-Unsubscribe: mailto:unsub+00ef1b38d61e7d79ec3a35a412cb372f49e7a71483c9eeaf92cf00000001169143dd92a169ce06071149@reply.github.com, https://github.com/notifications/unsubscribe/AO8bOERHSbEMs5jbaPr-LhATyPwy1qBPks5tSCfdgaJpZM4FsECW X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: hello@salmanwaheed.info X-SG-EID: 92ws1MVnlto3blxqXlf5goB0ee0kdDGWR6vcWx8d648REyn4hbxJw1z/ZZvtDz0Rm0fgcIImo3hMxA 86oyE293EwL24SmkiTUTEax/Kj7u5NTNfMxpTrDl8X5xzYlGFY5if07oj9rtbGWdhf3MEz3pR2IslT klWVqJc+/QNR+dHgo1srsgIbr8QVuoAxHIuEevFXwpT/8wmN346jY5M5ijsVvY/e8/zrAovLSn1slT c= X-Spam-Status: No, score=0.2 X-Spam-Score: 2 X-Spam-Bar: / X-Ham-Report: Spam detection software, running on the system "box1177.bluehost.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details.

Content preview: Closed #1449. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/aws/aws-cli/issues/1449#event-1459787911 Closed #1449. [...]

Content analysis details: (0.2 points, 5.0 required)

pts rule name description

0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: github.com] -0.5 SPF_PASS SPF: sender matches SPF record -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.7 HTML_IMAGE_ONLY_20 BODY: HTML: images with 1600-2000 bytes of words -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 2.5 DCC_CHECK No description available. -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.5 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2) [192.254.113.101 listed in wl.mailspike.net] -1.9 AWL AWL: Adjusted score from AWL reputation of From: address X-Spam-Flag: NO

----==_mimepart_5a7981dd3ccbd_8363fbb60110f3476784 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1449.

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/aws/aws-cli/issues/1449#event-1459787911 ----==_mimepart_5a7981dd3ccbd_8363fbb60110f3476784 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1449.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a7981dd3ccbd_8363fbb60110f3476784--

kenorb commented 6 years ago

GH-404: Add rsync-like --update to s3 sync
GH-2874: Add --no-overwrite option to aws s3 cp/mv
Suggestion: Add --no-overwrite option to aws s3 cp/mv
Suggestion: aws s3 sync --existing
Suggestion: Add rsync-like --update to s3 sync

jamesls commented 6 years ago

Based on community feedback, we have decided to return feature requests to GitHub issues.

landsman commented 2 years ago

Based on community feedback, we have decided to return feature requests to GitHub issues.

Very good choise

lachesis commented 1 year ago

So... glad to hear discussion is back on Github. Is this feature going to be implemented at some point? What would need to happen to move it forward?

I'm about to write this myself (and I'm sure I'm not the first). My case is easy because I have no "directories" (or paths with / in s3). My script will be roughly:

aws s3 ls s3://$bucket | sort > remote
find $local_path | sort > local
comm -23 local remote | parallel aws s3 cp $local_path/{} s3://$bucket/{}

aws / aws-cli

aws s3 sync --existing #1449