Olaf Conijn

org-formation perform-tasks ./organization-tasks.yml --no-color --state-bucket-name organization-formation-705671790868 --state-object state.json --print-stack

--print-stack prints the stacktrace of any error to the output. I do realize (only now?) that the term stack got overloaded quite a bit :D

hi @nbaillie org-formation allows you to register types into the cloud-formation resource registry. the organization.yml however is not being executed/processed by CloudFormation. the intention behind this issue was to document...

Great! Would be happy to help by providing performance measurements or otherwise 👍

what happen with these expressions is that they do not resolve before getting added to the templating context, but they are copied over as expressions. MyAccount: {{ MasterAccount }} will...

the error is correct/ the expactation is not. From context, I understand that the aws-sso.yml contains at least 1 CloudFormation resource (PermissionSet) that does not have a OrganizationBinding. The DefaultOrganizationBinding...

how bindings are used depends on the template you are trying to deploy. it seems like TargetBinding is set to {Account: *}, which might be binding that you are looking...

My guess is that you came across a template for implementing AWS SSO somewhere and copied this in your project. example: - task [here](https://github.com/org-formation/org-formation-reference/blob/c865611bc55ff0d727fefbb92e38faa56a61afa3/src/templates/100-aws-sso/_tasks.yml#L33-L51) - template [here](https://github.com/org-formation/org-formation-reference/blob/master/src/templates/100-aws-sso/aws-sso.yml) in this example...

I think the confusion is about the following: - cross-account-role, this is the role that will be used to set up new accounts. it will also be pass into roleName...

thanks @brianmyburgh, I havent read up on the changes yet. But how would parameters be passed to Serverless workloads? I would assume there to be an alternative/workaround