[EPIC] Amazon S3 Destination to GA

[alexandr-shegeda]

The main purpose of this issue is to track release progress for the connector.

Acceptance criteria

• Create a checklist document that should be placed on the Google Drive
• Checklist filled up by engineering team
• Create/Revise MLP document and place it here
• Collect and list all tech debt-related issues in the section below
• Move checklist to the unblockers team
• Reviewed/Updated by unblockers team
• Move checklist to the product team for review
• Reviewed/Updated by product team
• Update connector documentation according to the comments in the checklist
• Certification completed

Outstanding Bugs

MLP section

In this section, all required features should be listed

Nice to have

• Make S3 output filename configurable #4184
• Destination S3: Not able to edit/save configuration for existing connections #10940
• Skip generating empty files - S3 destination #7587
• S3 Destination hangs on overwrite #5128

Must have

[sashaNeshcheret]

@misteryeo Please take a look at description and linked docs.

[misteryeo]

Reviewed checklist and added some outstanding items.

[misteryeo]

Reviewed checklist @sashaNeshcheret

[sashaNeshcheret]

@misteryeo could you check list of Outstanding Bugs in 'Nice to have' section to verify that no one is not blocking going s3 to GA?

[misteryeo]

LGTM @sashaNeshcheret!

[misteryeo]

@sashaNeshcheret reviewed - checklist looks good overall but it looks like the changes you made to the input fields were in markdown instead of HTML. I've gone and updated them here: #12797

[sashaNeshcheret]

@misteryeo I've published and merged #12797, as far as we finishing with certification I can proceed with updating the releaseStage in the connector index and the Connector Status in release sheet, correct? Also could you update your review point in epic description and appropriate cells in excel doc.

[misteryeo]

@sashaNeshcheret checklist has been reviewed?

#12797 doesn't look like it's been deployed into Cloud - I mentioned this in Slack and asking @grishick for help as well. But besides that, those next steps make sense to me assuming this gets deployed.

[grishick]

FYI, I opened a PR to bump this connector's version in cloud: https://github.com/airbytehq/airbyte-cloud/pull/1674

[grishick]

@misteryeo the new connector version has been published into Airbyte Cloud. Please confirm if it's good to be called GA now and then we can change the label to GA.

[misteryeo]

LGTM @grishick @sashaNeshcheret

[sashaNeshcheret]

I updated release stage for OSS and cloud and add PRs to doc, @misteryeo should we use new version of certification doc or we can use existing one, and could you fill in "Product" rows.

[misteryeo]

The certification doc you've used now is fine - I've reviewed and LGTM thanks @sashaNeshcheret