Coen Meulenkamp

Be mindful that there is also an effort to integrate this into the lemmy backend: https://github.com/LemmyNet/lemmy/issues/2870 EDIT: 'effort' might have too big of a word, maybe 'open ticket' suited better.

There is a pragmatic fix: ```diff diff --git a/src/rpdk/core/project.py b/src/rpdk/core/project.py index bbf0922..b0870ae 100644 --- a/src/rpdk/core/project.py +++ b/src/rpdk/core/project.py @@ -509,6 +509,7 @@ class Project: # pylint: disable=too-many-instance-attributes,too-many-public-m if "typeConfiguration" in self.schema:...

I found the appropriate schema for type configuration: https://github.com/aws-cloudformation/cloudformation-cli/blob/master/src/rpdk/core/data/schema/provider.configuration.definition.schema.v1.json This one does not allow for the 'remote'-attribute. I will be closing the pull request as my 'pragmatic' fix won't be...

I am currently resolving this by pulling in the remote schemas by myself, and embedding them before I hand it to `cfn package`.

How did you install Python, and how are you running cfn-cli? If cfn-cli or Python was installed via brew, I noticed this occurring with many of my tools that used...

I am encountering the same issue. Due to this test, any resource that updates and tracks a remote identifier which is used for retrieving said resource will fail.