testing both approaches here: adding additional Limitations for an API operation using either a specific decorator kms_api.CreateKey or a generic one ApiLimitation.

• the second option ApiLimitation can be reused for every operation, and we can provide the actual limitations as input (currently string, but we could change this to a list as well).
  • if there are a lot of limitations we could use constants that are defined in a separate file, to not pollute the code too much
  • tested this approach in the playground.py script, e.g. it will be added as api_limitation:

          "Provisioning": {
          "docs": {
            "general_docs": "Manage the creation and modification of the keys.",
            "implementation_status": "ImplementationStatus.FULLY_IMPLEMENTED",
            "support_type": "SupportStatus.SUPPORTED",
            "aws_docs_link": "https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html",
            "api_operations": [
              "CreateKey"
            ]
          },
          "operations": [
            "localstack.services.kms.provider.KmsProvider.create_key",
            "localstack.services.kms.provider.KmsProvider.update_key_description"
          ],
          "api_limitations": {
            "localstack.services.kms.provider.KmsProvider.create_key": "Status 'Updating' is not supported."
          }
        },
  

i had to remove the empty handlers, as these somehow interfered with the tests in asf_utils.py - didn't investigate further, I am sure we could solve this and keeping the handler. On the other hand the handler doesn't do anything here :)

moved the script and adapted the paths. Originally added by @sannya-singal in #11593