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

[Bug]: CfnTrigger prop tolerateResumeErrorsis not respected #350

Closed
2 tasks done
Dragomirc opened this issue Sep 9, 2024 · 2 comments
Closed
2 tasks done

[Bug]: CfnTrigger prop tolerateResumeErrorsis not respected #350

Dragomirc opened this issue Sep 9, 2024 · 2 comments

Comments

@Dragomirc
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

CDK package version

2.141.0

CFN Resource version

NA

CFN Resource Region

eu-west-1

Current Behavior

When the tolerateResumeErrors prop is set to true, it does not appear to be respected during the CDK deployment. After deployment, checking the MongoDB Atlas UI shows that the auto-resume feature remains disabled, despite the expectation that it would be enabled.

Expected Behavior:
Setting tolerateResumeErrors: true should enable the auto-resume feature in MongoDB Atlas upon deployment.

Current Behavior:
Even with tolerateResumeErrors set to true, the MongoDB Atlas UI shows that the auto-resume feature is disabled after deployment.

AWS CDK code to reproduce the issue

new CfnTrigger(this, "Trigger", {
      projectId: props.projectId,
      type: "DATABASE",
      name: props.triggerName,
      profile: props.mongoProfileName,
      appId: props.appId,
      databaseTrigger: {
        operationTypes: [
          DatabaseConfigOperationTypes.INSERT,
          DatabaseConfigOperationTypes.DELETE,
          DatabaseConfigOperationTypes.UPDATE,
          DatabaseConfigOperationTypes.REPLACE,
        ],
        database: props.database,
        collection: "articles",
        serviceId: props.serviceId,
        fullDocumentBeforeChange: true,
        fullDocument: true,
        tolerateResumeErrors: true,
        match: `{}`,
      },
      eventProcessors: {
        awseventbridge: {
          awsConfig: {
            accountId: props.account,
            region: props.region,
          },
        },
      },
    });

Steps To Reproduce

  1. Set the tolerateResumeErrors prop to true in the CDK configuration.
  2. Deploy using CDK.
  3. Check the MongoDB Atlas UI to see if the auto-resume feature is enabled.
  4. Observe that the feature remains disabled.

cdk synth

HarvesterStoreharvesterArticlesTrigger19BD6910:
    Type: MongoDB::Atlas::Trigger
    Properties:
      Profile: <profile name>
      DatabaseTrigger:
        ServiceId: <service id>
        Database: <database name>
        Collection: <collection name>
        OperationTypes:
          - INSERT
          - DELETE
          - UPDATE
          - REPLACE
        Match: "{}"
        Project: "{}"
        FullDocument: true
        FullDocumentBeforeChange: true
        TolerateResumeErrors: true
      Name: <name>
      Type: DATABASE
      EventProcessors:
        AWSEVENTBRIDGE:
          AWSConfig:
            AccountId: <account id>
            Region: eu-west-1
      AppId: <app id>
      ProjectId: <project id>
    Metadata:
      aws:cdk:path: ServiceStack/HarvesterStore/harvesterArticlesTrigger

Code of Conduct

  • I agree to follow this project's Code of Conduct
Copy link

github-actions bot commented Sep 9, 2024

Thanks for opening this issue! Please make sure to provide the following information to help us reproduce the issue:

  • CDK code used by the customer
  • The output of cdk synth
  • List of Public CFN Resources that are activated in the AWS account with their release version
  • AWS Region where the CFN stack is running

Thanks for opening this issue. The ticket CLOUDP-272425 was created for internal tracking.

@maastha
Copy link
Collaborator

maastha commented Sep 17, 2024

Hi @Dragomirc

We are already tracking this issue in https://jira.mongodb.org/browse/CLOUDP-273338. We currently don't have an ETA for the fix.
Closing this issue as duplicate.

@maastha maastha closed this as completed Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants