Skip to content

AWS CloudFormation Git Sync - can't turn off comments on pull request?

0

We have Git sync configured for our CloudFormation stacks. It works great. But we frequently hit the rate limit for AWS Github app (5000 api calls per hour). We want to turn off this setting below (comments on pull request) so that we can prevent unnecessary Github API calls, that'll also help us stay under the rate limit. But we can't seem to turn this setting off.

AWS Cloudformation "Comment on Pull Request" setting

When we toggle this off and then click on "Save". The toggle will still be turned on after we refresh the page.

Is this an issue with AWS? How can we disable this?

asked a year ago136 views

1 Answer
1

Hello.

Please check whether the status of "PullRequestComment" is "DISABLED" using the command below.
If it is "DISABLED", the settings have been saved successfully.
For "githubtest", enter the name of your CloudFormation stack.
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/codeconnections/get-sync-configuration.html

aws codeconnections get-sync-configuration --sync-type CFN_STACK_SYNC --resource-name githubtest

Try running AWS CLI commands from CloudShell.
https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html

When you run the command, you can see the following response.

{
    "SyncConfiguration": {
        "Branch": "main",
        "ConfigFile": "GuardDuty.yml",
        "OwnerId": "Kobayashi-Riku0226",
        "ProviderType": "GitHub",
        "RepositoryLinkId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyy",
        "RepositoryName": "CloudFormation",
        "ResourceName": "githubtest",
        "RoleArn": "arn:aws:iam::123456789012:role/service-role/githubtest",
        "SyncType": "CFN_STACK_SYNC",
        "PublishDeploymentStatus": "ENABLED",
        "TriggerResourceUpdateOn": "ANY_CHANGE",
        "PullRequestComment": "DISABLED"
    }
}

In the management console, when you open the edit screen, the toggle is enabled, but if you have successfully saved the settings, you should be able to disable it.

EXPERT

answered a year ago

AWS
EXPERT

reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.