Feature/1409 deploy noupdate flag that limits deploy to create

[JoernBerkefeld]

PR details

What changes did you make? (Give an overview)

• closes [FEATURE] deploy --noUpdate flag that limits deploy to create #1409

Further details (optional)

...

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• test scripts updated
• Wiki updated (Feature/1409 deploy noupdate flag that limits deploy to create #1427 (comment))

[github-actions]

Coverage Report

Commit:5c8d4a9
Base: develop@182011d

Type	Base	This PR
Total Statements Coverage	69.2%	69.2%  (+0%)
Total Branches Coverage	67.71%	67.85%  (+0.14%)
Total Functions Coverage	80.85%	80.85%  (+0%)
Total Lines Coverage	69.2%	69.2%  (+0%)

Details (changed files):

File	Statements	Branches	Functions	Lines
lib/cli.js	0%	0%	0%	0%
lib/index.js	70.3%	60%	72.97%	70.3%
lib/metadataTypes/DataExtension.js	81.02%	69.94%	94.28%	81.02%
lib/metadataTypes/Event.js	85.88%	64.7%	100%	85.88%
lib/metadataTypes/Folder.js	54.89%	64.61%	80%	54.89%
lib/metadataTypes/MetadataType.js	80.45%	76.92%	73.97%	80.45%

[JoernBerkefeld]

Documentation

deploy

Command: mcdev deploy [business unit] [metadata type] [metadata key] [--metadata] [--fromRetrieve] [--refresh] [--keySuffix] [--noMidSuffix] [--changeKeyValue=yourNewKey] [--changeKeyField=otherFieldInJson] [--execute] [--schedule] [--fixShared] [--noUpdate]

...

deploy with --noUpdate

If you want to ensure that your deployment does not override existing metadata but instead is limited to creating new elements, then add the --noUpdate option to your call.

mcdev deploy cred/bu --noUpdate