Olaf Conijn

yes you are right: Started to use the type myself and indeed realized that taking ownership of all PrincipalId's is too rigid. doesn't work. Fixed that by adding a UUID...

@benkehoe, to round up the options: 1. serializing data in the primaryIdentifier (workaround) 2. storing state somewhere else (give the resource a name > make it resource oriented towards the...

To put everything together - `Community::SSO::PrincipalAssignments` gets a name attribute (required) - `Community::SSO::PrincipalAssignments` gets a StrictModel attribute (optional, default is false) - `Community::SSO::PrincipalAssignments` gets a RPStateBucket attribute (required in StrictMode)...

Yep, also like that idea! Seems like moving the same problem somewhere else, but if you can solve this in a somewhat scalable way.... impressive :)

I ran into more cases where strict adherence to the RP contract was something you might want to opt-in for. In this case adherence to the contract (ReadHandler) requires users...

Name for this resource should be different by now... something more like: `Community::SSO::AssignmentGroup` ? Just notices something different too: you added a AWS_OU TargetType to your resource. What would you...

> Why wouldn't the physicalId just be the name? I thought of something ARN like as this indicates whether the resource is regional (contains region), accountId, type and name. >...

interesting! will definitely have a look. thanks for posting

Because of the create semantics. You can't create a default VPC if its already there (so adding the resource would fail by default). Removing the resource shouldn't remove something that...

great! yes ~ we should bit the bullet on this :). now, i know more or less [the interface a plugin should adhere to](https://github.com/org-formation/org-formation-cli/blob/master/src/plugin/plugin.ts). what would be a good mechanism...