fix(cdk-lib): multiple submodules use an incorrect namespace for .NET

[mrgrain]

Issue

53 submodules of aws-cdk-lib used the wrong .NET package name.

Example:

# ❌  wrong
Amazon.CDK.aws_bedrockagentcore

# ✅ correct
Amazon.CDK.AWS.BedrockAgentCore

❌ wrong

✅ correct

Full list of affected submodules:

aws-aiops
aws-applicationsignals
aws-apptest
aws-arcregionswitch
aws-arczonalshift
aws-b2bi
aws-backupgateway
aws-bcmdataexports
aws-bedrock
aws-bedrockagentcore
aws-billing
aws-cleanrooms
aws-cleanroomsml
aws-codeconnections
aws-connectcampaignsv2
aws-datazone
aws-deadline
aws-dsql
aws-entityresolution
aws-evs
aws-gameliftstreams
aws-healthimaging
aws-invoicing
aws-launchwizard
aws-mediapackagev2
aws-mpa
aws-neptunegraph
aws-notifications
aws-notificationscontacts
aws-observabilityadmin
aws-odb
aws-osis
aws-paymentcryptography
aws-pcaconnectorad
aws-pcaconnectorscep
aws-pcs
aws-proton
aws-qbusiness
aws-rbin
aws-route53profiles
aws-rtbfabric
aws-s3express
aws-s3tables
aws-s3vectors
aws-securitylake
aws-shield
aws-smsvoice
aws-ssmguiconnect
aws-ssmquicksetup
aws-verifiedpermissions
aws-workspacesinstances
aws-workspacesthinclient
aws-workspacesweb

Reason for this change

The name of submodules is determined by a .jsiirc.json‎ inside the submodule directory. If not present, the export name is appended to the name of the parent module. However for most jsii languages this convention is not great: JavaScript export names don't translate well into other ecosystems.

For aws-cdk-lib we therefore have added .jsiirc.json‎ files into each submodule. For new services, this file is generated when the service is first added. Due to a bug, this generated file was incorrectly adding the key package to the dotnet target configuration. It should have been namespace instead.

Since this was a mistake, we are fixing this now. It means that the package names for the listed 53 submodules are changing for .NET users.

Description of changes

Update the package names of the listed 53 submodules to use the correct configuration.

Adjusted the order of targets in other .jsiirc.json files to be the same as generated ones.

Describe any new or updated permissions being added

n/a

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]

(This review is outdated)

✅ 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).

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #36002 has been dequeued. The pull request rule doesn't match anymore. The following conditions don't match anymore:

• -label~=(blocked|do-not-merge|no-squash|two-approvers|priority-pr)
• check-success=build
• check-success=validate-pr
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default-squash]
    • -label~=(blocked|do-not-merge|no-squash|priority-pr)
    • check-success=build
    • check-success=validate-pr
    • any of: [🛡 GitHub branch protection]
      • check-neutral = validate-pr
      • check-skipped = validate-pr
      • check-success = validate-pr
    • any of: [🛡 GitHub branch protection]
      • check-neutral = build
      • check-skipped = build
      • check-success = build.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[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).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.