fix(cli): direct deploy method fails when there are no updates

[jogold]

This is correctly handled for empty change sets here:

aws-cdk/packages/aws-cdk/lib/api/util/cloudformation.ts

Lines 290 to 296 in 9d8b06f

	export function changeSetHasNoChanges(description: CloudFormation.DescribeChangeSetOutput) {
	const noChangeErrorPrefixes = [
	// Error message for a regular template
	'The submitted information didn\'t contain changes.',
	// Error message when a Transform is involved (see #10650)
	'No updates are to be performed.',
	];

but not for direct updates.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

[jogold]

Exemption Request

This change doesn't need an integ test.

[aws-cdk-automation]

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

[go-to-k]

Looks good!

(I made a comment that I misunderstood and deleted that.)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 7ca49ee
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).