Chongsun Ahn

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.

There probably is a more robust way; I just did this as an incremental improvement.

There probably is a more robust way; I just did this as an incremental improvement.

This statement was necessary to go from 9.5.x to 9.6.x (https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion)...

This statement was necessary to go from 9.5.x to 9.6.x (https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion) It shouldn't upgrade to 10 or 11, since we specify engine version as 9.6.14. But if we did specify the engine version as 10 or 11, it might, based on the matrix in the link I posted. We do have PostGIS installed, so that would also affect what it gets upgraded to.

OLMIS-6425 Various provisioning and build changes
OLMIS-6425 Various provisioning and build changes
Thanks, I added the repo, and made a couple of comments.

Thanks, I added the repo, and made a couple of comments.

This stage is what I would prefer to be for the build jenkins job. Additionally, that way, if we wanted to deploy with a custom pg dump and eLMIS WAR file, we can do that instead of just using some...

This stage is what I would prefer to be for the build jenkins job. Additionally, that way, if we wanted to deploy with a custom pg dump and eLMIS WAR file, we can do that instead of just using something from the eLMIS git repo.

Can we change this so that we build the docker images in one jenkins job, and do the deployment in another jenkins job? Since it's not that important to see the latest eLMIS code when demonstrating...

Can we change this so that we build the docker images in one jenkins job, and do the deployment in another jenkins job? Since it's not that important to see the latest eLMIS code when demonstrating the pipeline, I would prefer to have a build process with a different cadence from the deployment process. This way, we're not also waiting for a whole eLMIS build when we redeploy the eLMIS server as well.

If we have this, we should have the correct copyright year.

If we have this, we should have the correct copyright year.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

a part

a part

comes from

comes from

Datetimes

Datetimes

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

Done.

Done.

OLMIS-6186 Set cron trigger to use config time zone
OLMIS-6186 Set cron trigger to use config time zone
Done.

Done.

Done.

Done.

What about chained function calls, like moment.tz().format()?

What about chained function calls, like moment.tz().format()?