Always 404 not found error when executing stackset deploy command

[kaito3desuyo]

I'm trying to deploy a CloudFormation StackSet, but I always get a 404 error on DescribeStackSetOperation.

$ rain stackset deploy example.yaml ExampleCFnStackSet --admin --config config.yaml
Stack set has been created successfuly with ID: ExampleCFnStackSet :81d4a89b-5628-40ad-b95f-9a89cac0f6c1
Submitted CREATE instances operation with ID: 62387382-145f-48fd-a0fd-984629683597
error while creating stack set instances: operation error CloudFormation: DescribeStackSetOperation, https response error StatusCode: 404, RequestID: 0dfe41ea-eae7-4003-b7bf-e2b52a6ab556, StackSetNotFoundException: StackSet ExampleCFnStackSet not found

If you look at the console, the StackSet is actually created.

When I run it again, the update tries to happen, but I get a 404 error again.

$ rain stackset deploy example.yaml ExampleCFnStackSet --admin --config config.yaml
Stack set already exists. Do you want to update it? (Y/n)
Updating stack set instances in all previously deployed accounts and regions
Submitted UPDATE stack set operation with ID: c5789d79-4535-42f1-b588-b748b65aa929
error occurred while updating stack set 'ExampleCFnStackSet' : operation error CloudFormation: DescribeStackSetOperation, https response error StatusCode: 404, RequestID: 59afd4cd-455e-465e-ab0f-b5f14f745dd8, StackSetNotFoundException: StackSet ExampleCFnStackSet not found

The configuration file is as follows.

StackSet:
  permissionmodel: SERVICE_MANAGED
  callas: DELEGATED_ADMIN
  capabilities:
    - CAPABILITY_NAMED_IAM
  autodeployment:
    enabled: true
    retainstacksonaccountremoval: false

StackSetInstances:
  deploymenttargets:
    organizationalunitids:
      - <OU ID>
  regions:
    - ap-northeast-1

[ericzbeard]

I'm diving into this and finding a number of bugs around parsing the config file and interacting with service managed stack sets. This will take me some time to sort out, hope to have an update next week.

[kaito3desuyo]

@Scribbd
All property names in the configuration file must be in lowercase. (as I am presenting)

[Scribbd]

Thank you. I didn't know and couldn't find documentation detailing this. I got my capitalization from tracing the types through rain and the go-sdk.
I will hide my comment.

EDIT: I had a go-journey to finally understand where this 'example' file is, and why the keys have to be lowercase. It took me to the inner workings of how go unmarshals yaml. I am creating a PR to make the piece of yaml readable on the github.io site, and a link directly to the example file. It was the wonky formatting and the absence of an actual reference to the example file that made me go down the go-type hole and assume the keys I used were valid.