When executing deploy, several situations can occur with the command indicating success in the logs but resulting in nothing being deployed.
The situations are:
- The
targetDirectory exists but is empty
- The
targetDirectory exists, is not empty, but contains no valid metadata files
- The server returned valid JSON from
GetDeployPlan but did not return a skuidMetadataService plan or a skuidCloudDataService plan
Regardless of which of the situations above occur, the user should be informed in an appropriate way (warning indicating nothing deployed and/or outright error) as currently, they could think their entire site deployed but nothing deployed.
Bonus item: When GetDeployPlan returns valid JSON and it contains a plan for skuidMetadataService and/or skuidCloudDataService but the plan doesn't contain complete information (e.g., missing the Host or Endpoint), the error emitted to the logs is HTTP 404 Not Found which is rather meaningless to a user so this error could be improved.
When executing
deploy, several situations can occur with the command indicating success in the logs but resulting in nothing being deployed.The situations are:
targetDirectoryexists but is emptytargetDirectoryexists, is not empty, but contains novalidmetadata filesGetDeployPlanbut did not return askuidMetadataServiceplan or askuidCloudDataServiceplanRegardless of which of the situations above occur, the user should be informed in an appropriate way (warning indicating nothing deployed and/or outright error) as currently, they could think their entire site deployed but nothing deployed.
Bonus item: When
GetDeployPlanreturns valid JSON and it contains a plan forskuidMetadataServiceand/orskuidCloudDataServicebut the plan doesn't contain complete information (e.g., missing theHostorEndpoint), the error emitted to the logs isHTTP 404 Not Foundwhich is rather meaningless to a user so this error could be improved.