I should be able to use the actual solution Id from package-solution.json when using the InstallSolution verb.
Observed Behavior
Currently I have to supply an internal Id only available when the solution is installed in an app catalog. This makes it very tedious and error prone to provision sites scripts through code, as I have no way of getting a clear binding between solution id and internal id. ALM API doesn't show the actual id of solution, only the internal id, even though the actual solution id is readily available in the app catalog. Because of this the only way to reference a solution beforehand is to use the ALM API and compare solution name, which is not exactly safe.
Category
Expected or Desired Behavior
I should be able to use the actual solution Id from package-solution.json when using the InstallSolution verb.
Observed Behavior
Currently I have to supply an internal Id only available when the solution is installed in an app catalog. This makes it very tedious and error prone to provision sites scripts through code, as I have no way of getting a clear binding between solution id and internal id. ALM API doesn't show the actual id of solution, only the internal id, even though the actual solution id is readily available in the app catalog. Because of this the only way to reference a solution beforehand is to use the ALM API and compare solution name, which is not exactly safe.