Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Versioned and DeltaSyncConfig #309

Closed
yyoshiki41 opened this issue Mar 2, 2020 · 2 comments · Fixed by #315
Closed

Support Versioned and DeltaSyncConfig #309

yyoshiki41 opened this issue Mar 2, 2020 · 2 comments · Fixed by #315

Comments

@yyoshiki41
Copy link

AppSync currently supports versioning on DynamoDB data sources.
https://docs.aws.amazon.com/appsync/latest/devguide/conflict-detection-and-sync.html

I want to configure this options.

Example of CloudFormation template is below.
we need Versioned and DeltaSyncConfig sections.

  DynamoDBPostsTableDatasource:
    Type: AWS::AppSync::DataSource
    Properties:
      Type: AMAZON_DYNAMODB
      Name: posts
      ApiId:
        Fn::GetAtt:
        - DeltaSyncApi
        - ApiId
      ServiceRoleArn: !GetAtt AppSyncTutorialAmazonDynamoDBRole.Arn
      DynamoDBConfig:
        TableName:
          Ref: DynamoDBTableDeltaSyncPostsTable
        AwsRegion:
          Ref: AWS::Region
        UseCallerCredentials: FALSE
        Versioned: TRUE
        DeltaSyncConfig:
          DeltaSyncTableName:
            Ref: DynamoDBTableDeltaSyncDeltaTable
          DeltaSyncTableTTL: 60
          BaseTableTTL: 0

thanks.

@yyoshiki41 yyoshiki41 changed the title Supports Versioned and DeltaSyncConfig Support Versioned and DeltaSyncConfig Mar 2, 2020
@bboure
Copy link
Collaborator

bboure commented Mar 2, 2020

Thank you @yyoshiki41
If you want to collaborate and open a PR to help with this, you are very welcome.

Useful resources:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-appsync-datasource-dynamodbconfig.html#cfn-appsync-datasource-dynamodbconfig-versioned

@yyoshiki41
Copy link
Author

@bboure

Thanks for your info!
I create a new pr to resolve this issue.
#313

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants