You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When choosing the import option then downloading the template, former2 generates the template yaml file and above this file it adds the resource ids in the following format (using AWS Organizations OUs and Accounts as examples):
While useful for visual confirmation, this format is not useful when importing the resources into CloudFormation which expects a json format like this:
Can former2 be changed to generate the correct json format needed by CloudFormation? This would save a lot of time and effort having to manually convert the comment format ids into the json format needed.
Thanks
The text was updated successfully, but these errors were encountered:
When choosing the import option then downloading the template, former2 generates the template yaml file and above this file it adds the resource ids in the following format (using AWS Organizations OUs and Accounts as examples):
While useful for visual confirmation, this format is not useful when importing the resources into CloudFormation which expects a json format like this:
and
Can former2 be changed to generate the correct json format needed by CloudFormation? This would save a lot of time and effort having to manually convert the comment format ids into the json format needed.
Thanks
The text was updated successfully, but these errors were encountered: