SHxKM

Hey @benbridts, thanks for the quick reply! `id` is both nested under `ourObj` and should be `readOnly`. Here's an obfuscated and trimmed schema: ```json { "typeName": "SomeComp::SomeProduct::SomeObj", "description": "SomeComp SomeProduct...

Thanks Ben. Both options are very undesirable as this is a product that’s in very wide use already, we just need it to pass tests at the moment as we...

@benbridts by the way I'm not sure how removing the nesting would help, I still need to return the ID to my end-users on read (or simply set it on...

I think my issue is very similar if not identical to this one. https://github.com/aws-cloudformation/cloudformation-cli/issues/646

The primaryIdentifier is generated at creation time and does not exist before it, so users can’t possibly pass it.

@benbridts OK. Yes. But the tests are still failing because the test I mentioned expects the input (what the user passed) to be like the output (what I return from...

Well that’s not what’s happening in the tests. create_read_success is expecting EXACTLY the same output from ReadHandler (at the read stage) as the input that was passed to CreateHandler (at...

@benbridts first off, I really appreciate your help and the fact that you are looking into this thoroughly. If you look at the thread that I linked above, issue number...

@benbridts - yep, I actually got the suite to pass by using a different version of `cli-cloudformation`, but only when the `primaryIdentifier` isn't nested..

Thanks @benbridts. > ...you can still only unnest the ID, as that will not be visible or specified to your users anyway Can you elaborate on this please? I'm not...