Chongsun Ahn

OLMIS-6473 Rename openlmisDatetime filter
OLMIS-6473 Rename openlmisDatetime filter
Feel free to add a more appropriate reviewer.

Feel free to add a more appropriate reviewer.

OLMIS-6464 Make redis cache persistent using configurable parameter
OLMIS-6464 Make redis cache persistent using configurable parameter
Looks good to me.

Looks good to me.

I don't think JSON supports comments. I think this is fine for now, and will resolve the issue.

I don't think JSON supports comments. I think this is fine for now, and will resolve the issue.

Looks good to me. And the YAML parameterization is pretty slick.

Looks good to me. And the YAML parameterization is pretty slick.

Looks good to me.

Looks good to me.

This is true. I'm just wondering if we want to allow these json files to have local dev default values in case someone wants to use them to re-register the connector and they don't have to edit the...

This is true. I'm just wondering if we want to allow these json files to have local dev default values in case someone wants to use them to re-register the connector and they don't have to edit the file before using it. What do you think?

Yeah, basically I was using one docker compose file for both local development and the automated deployment. Some containers were logging to syslog, while others were not and just logging to stdout...

Yeah, basically I was using one docker compose file for both local development and the automated deployment. Some containers were logging to syslog, while others were not and just logging to stdout. I separated local dev and automated deployment into separate docker compose files, and the automated deployment containers all log to syslog now, so that they can be captured by scalyr.

OLMIS-6461 Change hardcoded values to configurable values
OLMIS-6461 Change hardcoded values to configurable values
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.