Dashboard

OLMIS-5387: disabled slack notifications for branches

OLMIS-5387: disabled slack notifications for branches

OLMIS-5387: disabled slack notification for branches

OLMIS-5387: disabled slack notifications for branches

OLMIS-5387: disabled slack notification for branches

OLMIS-5387: disabled slack notifications for branches

OLMIS-5387: disabled slack notifications for branches

OLMIS-5387: disabled slack notifications for branches

OLMIS-4943 added locale settings to reports in Fulfillment
OLMIS-4943 added locale settings to reports in Fulfillment
OLMIS-4943 added changelog

Elias I still see template in some places like: ResourceServerSecurityConfiguration, VersionController

Elias I still see template in some places like: ResourceServerSecurityConfiguration, VersionController

OLMIS-4943 fixed Timestamp settings in Jasper report

I removed the field and related classes.

I removed the field and related classes.

I removed the field and related classes.

I removed the field and related classes.

OLMIS-4943 removed unnecessary values

OLMIS-5384: Removed unnecessary FHIR code

For now, we will only support DSTU3 version of FHIR server and we assume

that clients are using our implementation of FHIR server which

is only configured to support DSTU3. Also, mCSD is a profile of DSTU3 and

it is not supported on anything below DSTU3.

  1. … 15 more files in changeset.
OLMIS-4943 added locale settings to Jasper reports

Add NiFi Registry Deployment (#7)

* OLMIS-5086: Add NiFi Registry Deployment

Since OpenLMIS needs a shared NiFi Registry instance, add deployment

scripts for it (to be used with Jenkins).

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5086: Add Terraform Def For NiFi Reg Deploy

Since the shared NiFi Registry instance will be deployed on an AWS

instance, add the definitions for that setup in Terraform files.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5086: Add Docker Install Auto Scripts

Since the NiFi Registry host will have to have the Docker Daemon

running, create Ansible scripts for installing Docker and Docker Compose

on that host.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5231: Use Ansible Tasks For TLS Gen Process

Since Ansible is unable to generate enough entropy when running the

shell script for generating the TLS files in the Docker role, switch to

generating the TLS files using Ansible tasks.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5231: Add Ansible pip Dependencies

Since a bunch of people will be using the defined Ansible playbooks, add

a file with the required pip dependencies. Also add documentation on how

to install the pip and Ansible Galaxy dependencies.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* Fix formatting for NiFi Registry Terraform

Do this by running:

terraform fmt provision/terraform/modules/nifi-registry

terraform fmt provision/terraform/reporting/nifi-registry

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5231: Setup Docker from within uat Terraform

Run the Ansible playbook for setting up Docker and Docker Compose from

within the uat Terraform definitions.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* Fix formatting for uat Terraform

Do this by running:

terraform fmt provision/terraform/modules/uat

terraform fmt provision/terraform/uat

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* Rename Terraform Var docker-https-port

Rename the Terraform variable docker-https-port to something more

appropriate (docker-tls-port).

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5231: Add DeployGroup EC2 Tag to uat Build

Since the Docker dynamic inventory will only run on hosts that have the

EC2 tag DeployGroup with a value of docker-hosts, add it to the uat

deployments.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5289, add benin-demo env

* OLMIS-5289, start README for how to use Terraform and Ansible for new env

* OLMIS-5086: Use openlmis-reporting SSH Key

Use the openlmis-reporting SSH key (whose private key is backed up in

the aws-instance-keys S3 bucket) in the NiFi Registry deployment.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5231: Standardise Terraform AWS Cred Vars

Use the same variable names for the Terraform variables to hold the AWS

key ID and AWS secret key across the UAT and NiFi Registry setups. This

allows for users to get the values from the same Terraform environment

variable.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-5231: Add Terraform Setup Instructions

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

    • -0
    • +11
    /deployment/reporting_env/nifi-registry/.env
    • -0
    • +6
    /deployment/reporting_env/nifi-registry/config/Dockerfile
    • -0
    • +42
    /deployment/reporting_env/nifi-registry/docker-compose.yml
    • -0
    • +3
    /provision/ansible/.gitignore
    • -0
    • +16
    /provision/ansible/README.md
    • -0
    • +4
    /provision/ansible/ansible.cfg
    • -0
    • +9
    /provision/ansible/docker.yml
    • -0
    • +219
    /provision/ansible/inventory/ec2.ini
    • -0
    • +1708
    /provision/ansible/inventory/ec2.py
    • -0
    • +4
    /provision/ansible/inventory/hosts
  1. … 41 more files in changeset.
OLMIS-5387: temporarily broke the build for slack notification testing

OLMIS-5387: disabled slack notifications for branches

As long as the referencedata service can access resources in hapifhir, successfully authenticating, one seems enough to me.

As long as the referencedata service can access resources in hapifhir, successfully authenticating, one seems enough to me.

I agree. At the moment, the HAPI FHIR server is only configured to support DSTU3. mCSD is a profile of DSTU3. mCSD is not supported on anything below DSTU3.

I agree. At the moment, the HAPI FHIR server is only configured to support DSTU3. mCSD is a profile of DSTU3. mCSD is not supported on anything below DSTU3.

In lines 49 and 52 we are counting the sum of quantities/soh which are never null, so I assume sum also can't be null. Previously (before my changes) it wasn't checked.

In lines 49 and 52 we are counting the sum of quantities/soh which are never null, so I assume sum also can't be null. Previously (before my changes) it wasn't checked.

OLMIS-5384: Added authorization options for FHIR client
OLMIS-5384: Added authorization options for FHIR client
Same here. I am not sure if we should support other modes than generate a token (aka use tokens from the auth service). If the service should always use our HAPI FHIR server then we probably could ...

Same here. I am not sure if we should support other modes than generate a token (aka use tokens from the auth service). If the service should always use our HAPI FHIR server then we probably could remove other options. Am I right?

I am not sure if we need to handle all versions. If the service should always use our HAPI FHIR server then we probably could remove other options. Am I right?

I am not sure if we need to handle all versions. If the service should always use our HAPI FHIR server then we probably could remove other options. Am I right?