Re: Open Source tool to deploy/promote PostgreSQL DDL

On 11/07/18 11:04, Hustler DBA wrote:
> Thanks Adrian and Rich,
> I will propose sqitch to the client, but I think they want something 
> with a GUI frontend.
>
> They want to deploy database changes, track which environments the 
> change was deployed to, be able to rollback a change (with a rollback 
> script), track when and if the change was rolled back and in which 
> environment/database... so pretty much a deployment and tracking GUI 
> software with a frontend.
>
> In the past, for doing database deployments to Oracle, I created a 
> tool using PHP (frontend/backend), MySQL (repository to track 
> deployments and store deployment logs) and scripted the release 
> scripts for deployment and rollback, and had my tool manage the 
> scripts up the environments. The client is "looking" for something 
> more open source for PostgreSQL. Do we have anything similar to this?
>
> Neil
>
> On Tue, Jul 10, 2018 at 6:22 PM, Rich Shepard 
> <rshepard@appl-ecosys.com <mailto:rshepard@appl-ecosys.com>> wrote:
>
>     On Tue, 10 Jul 2018, Hustler DBA wrote:
>
>         A client of mine is looking for an open source tool to deploy
>         and promote
>         PostgreSQL DDL changes through database environments as part
>         of SDLC. What
>         tools (open source) does the community members use? I normally use
>         scripts, but they want something open source.
>
>
>     Neil,
>
>       I'm far from a professional DBA, but scripts are certainly open
>     source
>     because they're text files.
>
Being text files has nothing to do with being Open Source!  As I could 
send you a BASH script, or Java source code of a program, where they are 
under a Proprietary licence.

On the other hand, being a script could be open source, it all depends 
on the licence!

>
>       To track changes for almoste everything I highly recommend Git
>     for version
>     control. It's distributed and can handle most types of files. I
>     use it for
>     tracking coding projects and well as report and other text
>     documents that
>     are edited and revised prior to release.
>
>     Rich
>
>
Hi Neil,

Please bottom post, as that is the convention in these lists. This 
convention allows people to read the history, before reading the reply.  
Alternatively, you can intersperse your comments if that makes the 
context  easier to follow.  You can also omit large chunks that are no 
longer relevant, replacing them with "[...]".

Note that using scripts makes it easier to automate and to document, 
plus it gives you far more control.  With PostgreSQL I use psql, as it 
is easier to use than any GUI tool.  I use an editer to create SQL 
scripts and execute them from psql.  Note that you can use psql to 
execute SQL from within a BASH script.

Scripts once working and tested, can be reused and stored in git.  This 
is not something you can do with actions in a GUI!


Cheers,
Gavin