Jörn Berkefeld

This is set to true by default and then enforces that unknown params lead to errors. We should brainstorm about this @DougMidgley ... There are certainly pros and cons here.

current:  better: if credential is wrong, tell the user what is available in config if credential was found but bu was not, advice to run [reloadBUs](https://github.com/Accenture/sfmc-devtools/wiki/06.a-~-Admin-Commands#reloadbus) and alternatively show...

 we currently show this warning but instead we could 1. auto-fix it 2. offer to auto-fix it 3. tell the user how to fix it via mcdev manually

at first glance the automation-version of deploy() looks the same - except for the missing document()-execution in the automation-version. Should be tested thoroughly before removing it.

`retrieveTemplateREST` already exists now might have to add `retrieveTemplateSOAP` as well.

They are sunset apparently-- do retest before removing it if api access remains in place?! - related to #808

right now we handle the error, add a log.error and then return an empty object. Instead, we should throw an error (potentially with an improved error message like the one...

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior if you pass in 2..n keys for all types that use...

- this enhances #38

- split from #870 ## for TRIGGERED automations: https://help.salesforce.com/s/articleView?id=sf.mc_as_define_a_file_trigger_automation.htm&type=5 --> https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/automation-studio-create-trigger.html ``` Host: https://YOUR_SUBDOMAIN.rest.marketingcloudapis.com POST /automation/v1/automations/trigger Content-Type: application/json Authorization: Bearer YOUR_ACCESS_TOKEN { "fileTransferLocationKey": "S3_FTL", "filename": "new_registrations.csv", "relativepath": "marketing/2022_09_15", "deduplicationKey": "