During the pairwise testing of CDS with k8splugin and its config API endpoints several problems were identified

• config template and config value component had different names of parameters what makes it almost impossible to pair both in config-assign and config-deploy operations
• config components used type of the content artifact from profile upload component
• config value API results have different format depending on the endpoint used what was not considered
• rollback operations must be replaced with delete to remove only necessary configuration - not all of them
• config value component accepts only values passed as a string when resource assignment result should be used instead.