feature/982: added option to execute after deploy

[phjulia]

PR details

What changes did you make? (Give an overview)

• closes [FEATURE] add --execute option to deploy method #982

Added possibility to execute query after deploy

Is there anything you'd like reviewers to focus on?

...

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• N/A test scripts updated
• Wiki updated (via [TASK] Documentation for 5.2 #1007)

[JoernBerkefeld]

Where did you save the Text for the Wiki update? We can only publish the Wiki update when the feature was released :)

[phjulia]

Where did you save the Text for the Wiki update? We can only publish the Wiki update when the feature was released :)

for this one I didn't add it yet, it's not ready yet :-) I have some questions that I left as comments

Here is the documentation:

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

Alias: mcdev d

Deploys metadata to the specified Business Unit. Example:

mcdev deploy MyProject/DEV
Only metadata that you copied into the deploy directory will be deployed. Please keep in mind that the folder structure needs to be similar to what the retrieve command creates in the retrieve folder, including the credentials and Business Unit name.

Similarly to mcdev retrieve you can also use the interactive mode to select credential and/or Business Unit.

deploy and execute:

This is a special combination that will execute a query after creating or updating it on the server.

mcdev deploy --execute
mcdev deploy MyProject/DEV query "key1,key2" --execute
mcdev deploy MyProject/DEV query "key1" --fromRetrieve --execute

[JoernBerkefeld]

Please fix the error

[github-actions]

Coverage Report

Commit:fc53c6d
Base: develop@eb23409

Type	Base	This PR
Total Statements Coverage	46.07%	46.09%  (+0.02%)
Total Branches Coverage	36.91%	36.94%  (+0.03%)
Total Functions Coverage	53.03%	53.09%  (+0.06%)
Total Lines Coverage	45.99%	46.01%  (+0.02%)

Details (changed files):

File	Statements	Branches	Functions	Lines

[JoernBerkefeld]

Coverage Report

Commit:0e6dccd
Base: develop@f6640a1

Type	Base	This PR
Total Statements Coverage	46.04%	46.05%  (+0.01%)
Total Branches Coverage	36.98%	36.99%  (+0.01%)
Total Functions Coverage	52.89%	52.95%  (+0.06%)
Total Lines Coverage	45.96%	45.96%  (+0%)

Details (changed files):

File	Statements	Branches	Functions	Lines
lib/cli.js	0%	0%	0%	0%
lib/index.js	43.85%	39.71%	52%	43.85%
lib/metadataTypes/Query.js	86.95%	68.75%	95.45%	87.64%

This needs a new test added to the query test class :)

[phjulia]

Coverage Report

Commit:0e6dccd
Base: develop@f6640a1
Type
Base
This PR
Total Statements Coverage
 46.04%

 46.05%  (+0.01%)
Total Branches Coverage
 36.98%

 36.99%  (+0.01%)
Total Functions Coverage
 52.89%

 52.95%  (+0.06%)
Total Lines Coverage
 45.96%

 45.96%  (+0%)

Details (changed files):
File
Statements
Branches
Functions
Lines

lib/cli.js
 0%
 0%
 0%
 0%

lib/index.js
 43.85%
 39.71%
 52%
 43.85%

lib/metadataTypes/Query.js
 86.95%
 68.75%
 95.45%
 87.64%

This needs a new test added to the query test class :)

@JoernBerkefeld Not sure how can I test if the query actually executed? I added a test that only checks that no errors occurred, is that OK? Deploy should always return true or false regardless if queries were started or not.