You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
techfg
added a commit
to techfg/skuid-cli
that referenced
this issue
Oct 5, 2024
Note that some issues mentioned in skuid#229 were addressed inaf20e1e74ff14ee0bfeab32a2c95f060670fe3a0 or prior commits in skuid#205Resolvesskuid#229
Related af20e1e
When executing
deploy
, several situations can occur with the command indicating success in the logs but resulting in nothing being deployed.The situations are:
targetDirectory
exists but is emptytargetDirectory
exists, is not empty, but contains novalid
metadata filesGetDeployPlan
but did not return askuidMetadataService
plan or askuidCloudDataService
planRegardless 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 forskuidMetadataService
and/orskuidCloudDataService
but the plan doesn't contain complete information (e.g., missing theHost
orEndpoint
), the error emitted to the logs isHTTP 404 Not Found
which is rather meaningless to a user so this error could be improved.The text was updated successfully, but these errors were encountered: