Deploy using Powershell

Francisco Quintanilla

Vote:

I am trying to upload a package to a staging area but got this error when I use the command Get-EpiDeploymentPackageLocation:

API call failed! The error was: The remote server returned an error: (500) Internal Server Error.
{"success":false,"errors":["The destination resource group to upload package is missing for project:

What could have been missing?

#225804

Jul 27, 2020 21:12

Quan Mai

Vote:

Did you call Connect-EpiCloud before calling Get-EpiDeploymentPackageLocation ?

#225828

Jul 28, 2020 8:02

Francisco Quintanilla

Vote:

Yes, I did. This is the script I am using for testing:

Write-Host "Connecting..." 

Connect-EpiCloud -ClientKey PUerL3 -ClientSecret HMNLk1J8
 
Write-Host "Finding deployment location..." 
 
$packageLocation = Get-EpiDeploymentPackageLocation -ClientKey PUerL3 -ClientSecret HMNLk1J8 -ProjectId 45745254-d204

Write-Host $package

I just realized this is not working only for one of my projects. I tested the same script in another project and works correctly. Do I have to "activate" something in the server?

#225839

Edited, Jul 28, 2020 13:35

Francisco Quintanilla

Vote:

It turned out that the storage account was missing. I had to create a ticket to the support team. It is working now :)

#225966

Jul 31, 2020 12:54

Try our conversational search powered by Generative AI!

Deploy using Powershell