fix(ec2): exposed userDataCausesReplacement in BastionHostLinuxProps

[ashishdhingra]

Issue # (if applicable)

Closes #31348.

Reason for this change

When creating a Bastion host, customer is using instance's userData to write approved public keys to .ssh/authorized_keys. However, when changing the list of authorized keys, it does not trigger the instance to be replaced, so the modification has no effect.

Description of changes

Exposed userDataCausesReplacement in BastionHostLinuxProps. The value is passed down to downstream AWS::EC2::Instance resource.

Description of how you validated changes

Added unit and integration tests.

NOTE: Re-invoking Template.fromStack(stack) doesn't change the resource Id, so unit test uses 2 stacks. May be invoking Template.fromStack(stack) caches the results and doesn't refresh it.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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

[pahud]

If I just care the logicalId should be different, another option FYR

    const oldResourceIds = Object.keys(Template.fromStack(stackOld).findResources('AWS::EC2::Instance'));
    const newResourceIds = Object.keys(Template.fromStack(stackNew).findResources('AWS::EC2::Instance'));

    if (oldResourceIds.length === 1 && newResourceIds.length === 1) {
      const oldResourceId = oldResourceIds[0];
      const newResourceId = newResourceIds[0];
    
      expect(oldResourceId).not.toEqual(newResourceId);
      expect(oldResourceId).toBe(`BastionHostUserDataCausesReplacement985DBC41${oldHash}`)
      expect(newResourceId).toBe(`BastionHostUserDataCausesReplacement985DBC41${newHash}`)
    } else {
      throw new Error('Expected exactly one AWS::EC2::Instance resource in each stack');
    }