Add In HA Event Callback

.github/workflows/action.yml

@@ -0,0 +1,54 @@
+name: build
+
+on:
+  push:
+    branches:
+      - "*"
+  pull_request:
+    branches:
+      - "*"
+  workflow_dispatch:
+
+##
+# Adjust container-image for different Perl version
+# Adjust services-oracle-image for different OracleXE DB versions
+# Adjust container-env-ORACLEV for different InstantClient versions
+##
+jobs:
+  build-job:
+    name: Build Latest
+    runs-on: ubuntu-latest
+    container:
+      image: perldocker/perl-tester:latest
+    env:
+      ORACLEV: latest
+      ORACLE_USERID: kermit/foobar
+      ORACLE_DSN: 'dbi:Oracle://oracle:1521/XEPDB1'
+    services:
+      # Oracle service (label used to access the service container)
+      oracle:
+        # Docker Hub image (change the tag "latest" to any other available one)
+        image: gvenzl/oracle-xe:latest
+        # Provide passwords and other environment variables to container
+        env:
+          ORACLE_PASSWORD: adminpass
+          APP_USER: kermit
+          APP_USER_PASSWORD: foobar
+        # Forward Oracle port
+        ports:
+          - 1521:1521
+        # Provide healthcheck script options for startup
+        options: >-
+          --health-cmd healthcheck.sh
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 10
+    steps:
+      - uses: actions/checkout@v2
+      - run: apt-get update -y
+      - run: apt-get install -y libaio1 libaio-dev bc sudo alien
+      - run: sudo -E maint/scripts/03_install_oracle_instantclient_rpm.bash
+      - run: . /etc/profile
+      - run: perl -V
+      - run: cpanm DBI Test::NoWarnings
+      - run: perl Makefile.PL && make && make test

.gitignore

@@ -0,0 +1,16 @@
+pm_to_blib
+MYMETA.yml
+Makefile
+Makefile.old
+Oracle.bs
+Oracle.c
+Oracle.o
+Oracle.xsi
+blib
+MYMETA.json
+dbdimp.o
+mk.pm
+oci8.o
+DBD-Oracle*
+project.vim
+cpanfile

.mailmap

@@ -0,0 +1,20 @@
+Alex Muntada <[email protected]> <[email protected]>
+Dean Hamstead <[email protected]> <[email protected]>
+Dean Hamstead <[email protected]> <[email protected]>
+Dean Hamstead <[email protected]> <[email protected]>
+Dean Pearce <[email protected]> <[email protected]>
+H.Merijn Brand - Tux <[email protected]> <[email protected]>
+John Scoles <[email protected]>   <byterock@50811bd7-b8ce-0310-adc1-d9db26280581>
+Martin J. Evans <[email protected]> <[email protected]>
+Martin J. Evans <[email protected]> <[email protected]>
+Martin J. Evans <[email protected]> <[email protected]>
+Martin J. Evans <[email protected]> <[email protected]>
+Martin J. Evans <[email protected]> <mjevans@50811bd7-b8ce-0310-adc1-d9db26280581>
+Michael Portnoy <[email protected]>   <[email protected]>
+Mike O'Regan <[email protected]> <[email protected]>
+Tim Bunce <[email protected]>   <timbo@50811bd7-b8ce-0310-adc1-d9db26280581>
+Tim Bunce <[email protected]>   <[email protected]>
+Wesley Hinds <[email protected]> <[email protected]>
+Yanick Champoux <[email protected]> <[email protected]>
+Yanick Champoux <[email protected]> <yanick@50811bd7-b8ce-0310-adc1-d9db26280581>
+Yanick Champoux <[email protected]> <[email protected]>

CONTRIBUTING.md

@@ -0,0 +1,111 @@
+# CONTRIBUTING
+
+Thank you for considering contributing to {{ $dist }}.
+This file contains instructions that will help you work with
+the source code.
+
+## Repository branches structure
+
+The two main branches of this repository are:
+
+* **master**
+
+The main development branch. This branch has to
+be processed by Dist::Zilla to generate the
+code as it will appear in the CPAN distribution. See the
+next section for more details.
+
+* **releases**
+
+Contains the code as it appears on CPAN. Each official
+release is also tagged with its version.
+
+## Working on the master branch
+
+The distribution is managed with [Dist::Zilla][distzilla].
+This means than many of the usual files you might expect
+are not in the repository, but are generated at release time.
+
+However, you can run tests directly using the 'prove' tool:
+
+``` bash
+$ prove -l
+$ prove -lv t/some_test_file.t
+$ prove -lvr t/
+```
+
+In most cases, 'prove' is entirely sufficient for you to test any
+patches you have.
+
+You may need to satisfy some dependencies. The easiest way to satisfy
+dependencies is to install the last release -- this is available at
+https://metacpan.org/release/{{ $dist }}.
+
+If you use cpanminus, you can do it without downloading the tarball first:
+
+``` bash
+$ cpanm --reinstall --installdeps --with-recommends {{ $dist =~ s/-/::/gr }}
+```
+
+Dist::Zilla is a very powerful authoring tool, but requires a number of
+author-specific plugins. If you would like to use it for contributing,
+install it from CPAN, then run one of the following commands, depending on
+your CPAN client:
+
+``` bash
+$ cpan `dzil authordeps --missing`
+$ dzil authordeps --missing | cpanm
+```
+
+You should then also install any additional requirements not needed by the
+dzil build but may be needed by tests or other development:
+
+``` bash
+# cpan `dzil listdeps --author --missing`
+$ dzil listdeps --author --missing | cpanm
+```
+
+You can also do this via cpanm directly:
+
+``` bash
+$ cpanm --reinstall --installdeps --with-develop --with-recommends {{ $dist =~ s/-/::/gr }}
+```
+
+Once installed, here are some dzil commands you might try:
+
+``` bash
+$ dzil build
+$ dzil test
+$ dzil test --release
+$ dzil xtest
+$ dzil listdeps --json
+$ dzil build --notgz
+```
+
+
+## This Is Complicated. Is There an Easier Way?
+
+Actually, yes there is. You can also work directly on the `releases` branch,
+which corresponds to the code is generated by Dist::Zilla and
+correspond to what is uploaded to CPAN.
+
+It won't contain any of the changes brought to the codebase since the last
+CPAN release, but for a small patch that shouldn't be a problem.
+
+## Sending Patches
+
+The code for this distribution is hosted on [GitHub][repository].
+
+You can submit bug reports via the [repository's issue track][bugtracker].
+
+You can also submit code changes by forking the repository, pushing your code
+changes to your clone, and then submitting a pull request. Detailed
+instructions for doing that is available here:
+
+* https://help.github.com/
+* https://help.github.com/articles/creating-a-pull-request
+
+[distzilla]:  http://dzil.org/.
+[repository]: https://github.com/perl5-dbi/DBD-Oracle/
+[bugtracker]: https://github.com/perl5-dbi/DBD-Oracle/issues
+