ob1dev/Sitecore-Azure-PowerShell

Issues

• Use the ValidateSet for Azure Location.

  #13 opened 9 years ago by ob1dev
  1

• Extend the Publish-SitecoreSqlDatabase cmdlet to publish from BACPAC packages.

  #12 opened 9 years ago by ob1dev
  0

• Extend the Get-SitecoreAzureStorageAccount cmdlet with additional parameters.

  #3 opened 9 years ago by ob1dev
  1

• Extend the Import-SitecoreAzureSqlDatabas cmdlet with additional parameter.

  #4 opened 9 years ago by ob1dev
  1

• In the Publish-SitecoreSqlDatabase cmdlet, use the PSCredential type with parameters.

  #11 opened 9 years ago by ob1dev
  1

• Document the Publish-SitecoreSqlDatabase cmdlet

  #1 opened 9 years ago by ob1dev
  1

• The Export-SitecoreAzureSqlDatabase cmdlet has hardcoded path to SQL Server installation.

  #2 opened 9 years ago by ob1dev
  1

• In the Publish-SitecoreSqlDatabase cmdlet, the default value for the AzureResourceGroupLocation is hardcoded.

  #10 opened 9 years ago by ob1dev
  0

• In the Publish-SitecoreSqlDatabase cmdlet, the StorageAccountName and SqlServerName are not globally unique.

  #6 opened 9 years ago by ob1dev
  1

• The `Publish-SitecoreSqlDatabase` cmdlet must output the connection string.

  #9 opened 9 years ago by ob1dev
  1

• Implement Publish-SitecoreProject cmdlet

  #8 opened 9 years ago by ob1dev
  0

• Replace the ASR version of the Start-AzureSqlDatabaseImport cmdlet with ARM one.

  #7 opened 9 years ago by ob1dev
  0

• In the Get-SitecoreAzureSqlServerStatus cmdlet, the Progress Bar might appears twice.

  #5 opened 9 years ago by ob1dev
  0