Define additional microservice manifest configurations like cpu and memory at microservice creation

[PestusAtSAG]

The microservice artifact ships with the microservice manifest which has specific microservice configurations. Some of them like cpu and memory can't be changed (update) after deployment and only used at creation. However, the manifest is in the most microservice projects static defined, because it belongs to the build package which gets deployed. But there is often a need to define this resources (cpu and memory) dependent on the usage which is from customer to customer or environment to environment different. In order to achive this, it would be create to enhance the microservice creation command, so that the manifest gets manipulated by the defined arguments in the operation so that i can define the resources in my deployment pipelines differently.

Example:

c8y microservices create --file ./myapp.zip --manifest '{"resources": { "cpu": "0.5", "memory": "1024m"}}'

or

c8y microservices create --file ./myapp.zip --cpu 0.5 --memory 1024m

please also consider limits for "resources" https://cumulocity.com/docs/microservice-sdk/general-aspects/#microservice-manifest and "requestedResources".

[reubenmiller]

I'd be prefer a combination, so that you have nice tab-completed values for the common stuff like cpu and memory, and then use either the --template flag, or support --manifest which supports the jsonnet templating so you can customize all of the values if you know the data format etc.)