awsrm VS TF

It's because I build the tooling in way that Terraform resource names, such as aws_vpc, aws_instance, aws_iam_role, etc. can be used to find resources (with awsls) and delete them (with awsrm), instead of using the to me not so familiar and inconsistent AWS CLI (or CloudFormation) resource names with commands, such as aws ec2 describe-vpcs or aws ec2 delete-vpc (in some cases it's list instead of describe, e.g., for roles it's aws iam list-roles, which is hard to remember).

`; Written by XeroByte` `; Generates the User.ahk.api file to add custom function & label intellisense!` `; to initate: use BuildUserAhkApi(A_ScriptFullPath,1) from the main script` `; Requires: grep() by Titan/Polyethelene` [`https://github.com/camerb/AHKs/blob/master/thirdParty/titan/grep.ahk`](https://github.com/camerb/AHKs/blob/master/thirdParty/titan/grep.ahk) `; Reqiures: isDir() Function` `; Optionally include TF_Wrap() from the TF Library` [`https://github.com/hi5/TF/blob/master/tf.ahk`](https://github.com/hi5/TF/blob/master/tf.ahk) `TF_Wrap := "TF_Wrap" ; This is for a workaround to make the script still work even without the TF library - need to call the function dynamically.` `if(isDir(AhkScriptPath)){` `Loop, %AhkScriptPath%\*.ahk,0,1` `AhkApiText .= BuildUserAhkApi(A_LoopFileLongPath, 0, RecurseIncludes, Labels, WrapWidth, AhkApiPath, 1)` `}else{` `FileRead, ThisScriptTxt, %AhkScriptPath%` `; Retrieve Functions` `grep(ThisScriptTxt, "m)^\s*[a-zA-Z0-9_-]*\([^\)]*\)\s*\{(\s*;.*?$)*", MatchCollection,1,0,"§")` `loop, parse, MatchCollection, §` `{`

i am using tf (https://github.com/hi5/TF). Its a text editing library.