openlmis-deployment

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-6557 New TF config for uat and test and new stack for both servers
OLMIS-6557 New TF config for uat and test and new stack for both servers
OLMIS-6496 Stand up v3 reporting stack for Casper
OLMIS-6496 Stand up v3 reporting stack for Casper
changed notification service version to 4.1.2-SNAPSHOT
changed notification service version to 4.1.2-SNAPSHOT
Create aws_security_group resource for casper

TODO: actually use this security group

    • -0
    • +1
    /provision/terraform/modules/casper/main.tf
    • -0
    • +114
    /provision/terraform/modules/casper/network.tf
OLMIS-6466 Open port 3000 for Grafana for Casper

Do not expose 8083 externally

For Debezium Connect originally.

Fix casper-elmis to be part of the Casper security group

    • -0
    • +1
    /provision/terraform/uat/casper-elmis/main.tf
I don't really know how to check this is working or review it properly, but looks fine to me.

I don't really know how to check this is working or review it properly, but looks fine to me.

OLMIS-6427 ETL pipeline automated deployment
OLMIS-6427 ETL pipeline automated deployment
OLMIS-6424 Get demo data automatically loaded into Casper v3 serverFix load data SQL error
OLMIS-6424 Get demo data automatically loaded into Casper v3 serverFix load data SQL error
This needs to be manually done, since demo data is loaded after refresh-db profile is run.

This needs to be manually done, since demo data is loaded after refresh-db profile is run.

The v3 server is pegged to 3.6, so this field still exists in the schema.

The v3 server is pegged to 3.6, so this field still exists in the schema.

The v3 instance should be read-only and should not be allowed to change data.

The v3 instance should be read-only and should not be allowed to change data.

Hacky; decided to do this after starting up v3, as it's the simplest approach, vs. trying to load demo data and figure out how to keep v3 from wiping it.

Hacky; decided to do this after starting up v3, as it's the simplest approach, vs. trying to load demo data and figure out how to keep v3 from wiping it.

OLMIS-6427 Change Casper v3 server to v3.6

Do not use latest snapshot, as the code is unstable and changes quickly.