Power Platform GitHub Actions automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.
The CDS Configuration Migration Tool often swallows warnings/errors and just runs through. It requires manual inspection of the log file to glean what happened. It would be great if there was a way to allow the download of the log file that is a results of a running the Import-Data action (Export-Data would be nice too, although it's less common to have issues with that process). Currently I have to run the CDS Configuration Migration Tool manually with the same data file that I ran in a GitHub action and review my local log file to figure out what went wrong on individual executions. This isn't feasible for upper environments.
petrochuk
commented
1 year ago
The CDS Configuration Migration Tool often swallows warnings/errors and just runs through. It requires manual inspection of the log file to glean what happened. It would be great if there was a way to allow the download of the log file that is a results of a running the Import-Data action (Export-Data would be nice too, although it's less common to have issues with that process). Currently I have to run the CDS Configuration Migration Tool manually with the same data file that I ran in a GitHub action and review my local log file to figure out what went wrong on individual executions. This isn't feasible for upper environments.