Parent, ByteArray and a bunch of others should not be in the json.

core-postgresql + dependencies
tests???

FullName is used instead.

Will be used in Invoke-DBODeployment and possibly other commands to generate connection string.
Should accept [DBOpsConfig] and ConnectionType as a parameter.

...in both Invoke-DBODeployment and Install-DBOPackage

• Add core libs to the project
• Check code compatibility with Linux
• Tests for linux??

Should return more than a simple object returned from DbUp. Should probably be a custom class that would be accepted through a pipeline by future helper functions: send emails, invoke tSQLt tests, PowerBI reports, etc.

SQL code:

INSERT INTO [dbo].[Course] ([Title], [Credits])
     VALUES ( N'#{Title}$Title$#{Title}#', #{Credit} )
GO

Powershell:

New-DBOPackage -Path C:\Temp\dbops_test.zip -ScriptPath C:\Temp\dbops_test -Force;
Add-DBOBuild -Path C:\Temp\dbops_test.zip -ScriptPath C:\Temp\dbops_test -Type Unique -Build 1.0.4
$pkg = Get-DBOPackage -Path C:\Temp\dbops_test.zip
$pkg | Install-DBOPackage -Build 1.0.4 -SqlInstance '.\SQL2017' -Database Test1 -CreateDatabase -Variables @{Title='hello';Credit='2'}

dbup-mysql + dependencies

Right now it's mostly Write-Host/Verbose/Error. Switch to Write-PSFMessage/Stop-PSFFunction instead for better logging.

Basically, start processing it in an async manner, since it's already working async.

Extract/Install Dacpacs using SMO.

S C:\Lab\packages> $database.Deploy($package)
Exception calling "Deploy" with "1" argument(s): "A parameter cannot be found that matches parameter name 'ConnectionString'."

Will help a lot during ad-hoc deployments.

Possible root cause: $script:pkg/build/file used in the pester tests, that enforces objects to be shared across the tests. This is a bad design decision and tests should be re-written to be completely independent.

Should be able to export config from packages and config objects.

DbUp creates dictionaries as an output of the adhoc reader, all keys in the dictionary should be unique.
DbUp/DbUp#390

Probably, using EnsureDatabase parameter in SqlDatabase call

New-DBOConfig will be the same olde Get-DBOConfig with no parameters.
Export-DBOConfig will provide an interface to the SaveToFile($filename) functionality.

Stop-PSFFunction -EnableException $true does not return a terminating error.
Possible workaround: add return and try {} catch {} everywhere where classes are called

https://docs.microsoft.com/en-us/dotnet/api/system.io.packaging

$null = [System.Reflection.Assembly]::LoadWithPartialName('WindowsBase')
[System.IO.Packaging.ZipPackage]::Open($path)

It would be great if it has option to send email notification with query results

Add .Deploy($package) method to the SMO object to integrate with SMO and dbatools

Resets all values to defaults as defined in psm1. Will be using a brand new command Reset-PSFConfig recently created by @FriedrichWeinmann 🎉

Packages that can contain one (or maybe more than one) build version, however, only the latest build is ever deployed. Build version is never recorded to the schemaversions table: every script is stored without a build prefix.
Pretty much, your regular Install-DBOScript deployment from a folder, but stored as a package.

I'm not sure this one is really needed yet, as similar behavior could be achieved by using the same exact build version every time when such package is getting created, but we'll see.

Ideas so far:

• A new switch for New-DBOPackage (something like -Simple or -SingleBuild) that enables that behavior and enforces the version-less deployment history.
• Single-build packages seem to make more sense to avoid confusion during the deployment.

Allows to register/unregister scripts in the schema versions table to fine tune the deployment.
Should accept 2 parameter sets:

• -Package $pkg -Build 1.0
• -ScriptName "1.0\Folder\Script.sql"
  and use ad-hoc sql executor to add/remove entries to the schema versions table

Invoke-DBODeployment should become a fully internal command eventually, only accepting [DBOpsConfig] instead of all the variety of the configuration items. Wrapper functions Install-DBOPackage and Install-DBOScript (???) would prepare configuration objects and call Invoke-DBODeployment using one of the two available parameter sets: Package or Script.

Right now some of them seem opny to accept [DBOConfig] as a parameter, but they should also be able to extract configs from the package files/objects.

RIght now it's #{var} but there's no reason not to allow it to be definable by the PSF config.

Add Pre- and -Post scripts to the packages and possibly to builds.

New-DBOPackage -ScriptPath .\foo -PreScriptPath .\bar -PostScriptPath .\foobar

$var$ is a native dbUp variable template. Need to completely disable it, as dbops is not using it at all.

Basically, select scripts with unique Fullnames.

subj

Currently Get-DBOPackageArtifact only returns the path to the file. CI build should be done in a local folder, so there is a need for a convenient way of retrieving that file using single command. Copy-DBOPackageArtifact?

Gotta create an empty configuration object and override it instead of modifying existing config inside the package obj

Right now the module requires specific versions of packages. It should be possible to allow using MinimumVersion instead.

First off, this is looking amazing already and I can't wait to start using it as an easy alternative to Flyway! Thanks for the work so far on a very much needed utility :)

dbops Version: 0.3.4
PS Version: 5.1.14393.2368
Issue: When attempting to export a config file, this is the error returned:

PS C:\> (Get-DBOConfig -Configuration @{ DeploymentMethod = 'SingleTransaction'; Schema = 'dbo'}).SaveToFile('test.json')
Method invocation failed because [DBOpsConfig] does not contain a method named 'SaveToFile'.
At line:1 char:1
+ (Get-DBOConfig -Configuration @{ DeploymentMethod = 'SingleTransactio ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound

This one would be used later instead of Invoke-SqlCmd2 both internally and externally.

https://github.com/DbUp/DbUp/blob/master/src/dbup-core/Helpers/AdHocSqlRunner.cs

Expected behaviour:
New-DBOPackage ... -Match '\.sql$' includes files with the extension ".sql" from all subfolders.
Actual behavior:
It only includes files from the top folder. Recursive folders won't make the cut because they do not match the pattern.

From slack.
Add -Include, -Exclude and possibly -NoRecurse to control how child items in folders get added.

Summary

Using Invoke-DBOQuery, queries returning non-null data of type aclitem[] (for example pg_database.datacl) throw an error. This data should be gracefully returned

Repro

Given Set-DBODefaultSetting -Name rdbms.Type -Value PostgreSQL,

PS > Invoke-DBOQuery 'select cast(null as aclitem[]);'                                                          

aclitem
-------


PS > Invoke-DBOQuery "select cast(null as aclitem[]), cast('{=c/postgres}' as aclitem[]);" -Verbose              
VERBOSE: [17:50:25][Initialize-ExternalLibrary] Npgsql was found among the loaded libraries, assuming that the library is fully loaded
VERBOSE: [17:50:25][Invoke-DBOQuery] Establishing connection with PostgreSQL localhost
VERBOSE: Performing the operation "Executing query select cast(null as aclitem[]), cast('{=c/postgres}' as aclitem[]);" on target "localhost".
VERBOSE: [17:50:25][Invoke-DBOQuery] Executing sub-query select cast(null as aclitem[]), cast('{=c/postgres}' as aclitem[]);
[17:50:25][Invoke-DBOQuery] 42883: no binary output function available for type aclitem
Exception calling "GetResult" with "0" argument(s): "42883: no binary output function available for type aclitem"
At /Users/pvandivier/.local/share/powershell/Modules/PSFramework/1.1.59/PSFramework.psm1:3304 char:23
+         if (-not $Cmdlet) { throw $records[0] }
+                             ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], Exception
    + FullyQualifiedErrorId : dbops_Invoke-DBOQuery
PS > 

Full Error

PS > Invoke-DBOQuery "select cast(null as aclitem[]), cast('{=c/postgres}' as aclitem[]);"
[17:53:06][Invoke-DBOQuery] 42883: no binary output function available for type aclitem
Exception calling "GetResult" with "0" argument(s): "42883: no binary output function available for type aclitem"
At /Users/pvandivier/.local/share/powershell/Modules/PSFramework/1.1.59/PSFramework.psm1:3304 char:23
+         if (-not $Cmdlet) { throw $records[0] }
+                             ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], Exception
    + FullyQualifiedErrorId : dbops_Invoke-DBOQuery
PS > $error[0] | select *         

PSMessageDetails      : 
Exception             : System.Exception: Exception calling "GetResult" with "0" argument(s): "42883: no binary output function available for type aclitem" ---> 
                        System.Management.Automation.MethodInvocationException: Exception calling "GetResult" with "0" argument(s): "42883: no binary output function available for type 
                        aclitem" ---> Npgsql.PostgresException: 42883: no binary output function available for type aclitem
                           at Npgsql.NpgsqlConnector.<>c__DisplayClass161_0.<<ReadMessage>g__ReadMessageLong|0>d.MoveNext() in C:\projects\npgsql\src\Npgsql\NpgsqlConnector.cs:line 1034
                        --- End of stack trace from previous location where exception was thrown ---
                           at Npgsql.NpgsqlConnector.<>c__DisplayClass161_0.<<ReadMessage>g__ReadMessageLong|0>d.MoveNext() in C:\projects\npgsql\src\Npgsql\NpgsqlConnector.cs:line 1034
                        --- End of stack trace from previous location where exception was thrown ---
                           at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming) in C:\projects\npgsql\src\Npgsql\NpgsqlDataReader.cs:line 526
                           at Npgsql.NpgsqlCommand.ExecuteDbDataReader(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken) in 
                        C:\projects\npgsql\src\Npgsql\NpgsqlCommand.cs:line 1231
                           at CallSite.Target(Closure , CallSite , Object )
                           --- End of inner exception stack trace ---
                           at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
                           at lambda_method(Closure , Object[] , StrongBox`1[] , InterpretedFrame )
                           --- End of inner exception stack trace ---
TargetObject          : 
CategoryInfo          : NotSpecified: (:) [], Exception
FullyQualifiedErrorId : dbops_Invoke-DBOQuery
ErrorDetails          : 
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at Stop-PSFFunction, /Users/pvandivier/.local/share/powershell/Modules/PSFramework/1.1.59/PSFramework.psm1: line 3304
                        at Invoke-DBOQuery<Process>, /Users/pvandivier/repos/git/dbops/functions/Invoke-DBOQuery.ps1: line 386
                        at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}


PS > 

For clarity on what's being added as well as to track progress.

Otherwise, the deploy1.ps1 file would fail to load the module.

https://github.com/pester/Pester/wiki/TestDrive

Importing the dbops module in the deploy.ps1 file does not load the DBOpsConfig class referenced on line 46.

Issue should be solved by sourcing . "$PSScriptRoot\Modules\dbops\internal\classes\DBOps.class.ps1"