Philip Garrison

OLMIS-6537 Update reporting documentation
OLMIS-6537 Update reporting documentation
OLMIS-6496 Stand up v3 reporting stack for Casper
OLMIS-6496 Stand up v3 reporting stack for Casper
Let's see... if you run the pipeline (locally) from e70d5c2 and watch the logs for the nifi container, you should see it takes quite a while and maybe has error messages like "<something> cannot be...

Let's see... if you run the pipeline (locally) from e70d5c2 and watch the logs for the nifi container, you should see it takes quite a while and maybe has error messages like "<something> cannot be updated because it is not disabled"

Yes, I read through the script there; was happy to learn about xmlstarlet. When I accidentally uploaded all the templates without the containing process groups, it took super long to upload: lots o...

Yes, I read through the script there; was happy to learn about xmlstarlet.
When I accidentally uploaded all the templates without the containing process groups, it took super long to upload: lots of retrying due to maybe conflicting processors. Not sure if that's something we can avoid here, especially since it doesn't look like this script does any retrying.

Pipeline seems to be working, and it did successfully upload templates.

Pipeline seems to be working, and it did successfully upload templates.

OLMIS-6459 Make Casper eLMIS redeployment process an "in-place upgrade"
OLMIS-6459 Make Casper eLMIS redeployment process an "in-place upgrade"
Built successfully: https://gitlab.com/openlmis/casper-deployment/-/jobs/258644410 Server: https://casper-elmis.a.openlmis.org
Ah okay, like re-registering from the curl command or from some debezium UI? Maybe then it's best to just leave a comment in the json file. We could include the full "key": "value" in the sed comma...

Ah okay, like re-registering from the curl command or from some debezium UI?
Maybe then it's best to just leave a comment in the json file.
We could include the full "key": "value" in the sed command to reduce the risk of editing the wrong thing, but that probably isn't worth it

OLMIS-6446 Change Casper v3 automated deployment process to use GitLab CI
OLMIS-6446 Change Casper v3 automated deployment process to use GitLab CI
You can check out the newly deployed server at https://casper.a.openlmis.org I learned about a new YAML feature that I used to make the KEEP_OR_WIPE parameter work; you can see just that change he...

You can check out the newly deployed server at https://casper.a.openlmis.org

I learned about a new YAML feature that I used to make the KEEP_OR_WIPE parameter work; you can see just that change here: https://gitlab.com/openlmis/casper-deployment/commit/428794bd25bde56aa5d1df34ed9e89b0a67ffaea

OLMIS-6445 Change Casper eLMIS automated deployment process to use GitLab CI
OLMIS-6445 Change Casper eLMIS automated deployment process to use GitLab CI
By pinning the build to a specific commit from the v2 source, we will have to be manually updating this to keep it recent. It's debatable whether we should do this pinning, but I've included it sin...

By pinning the build to a specific commit from the v2 source, we will have to be manually updating this to keep it recent. It's debatable whether we should do this pinning, but I've included it since the commit after this seems to cause issues with the build.
The pinned commit here is from July 17.

The changesets included here also add some logging. Not sure if that should have some jira/crucible infrastructure/documentation around it. Some commit messages document the logging changes, but ot...

The changesets included here also add some logging. Not sure if that should have some jira/crucible infrastructure/documentation around it. Some commit messages document the logging changes, but others (2dae5eb) don't. Seems like a minor issue we can just ignore though

If we use obvious variable names like V3_PG_USERNAME as the default values in the json file, it will be apparent from reading it that they get modified somewhere. This could also avoid problems if,...

If we use obvious variable names like V3_PG_USERNAME as the default values in the json file, it will be apparent from reading it that they get modified somewhere. This could also avoid problems if, for instance, someone adds "postgres" as a key somewhere in the json file

Initial commit

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.

There may be a way to look up the group ID automatically? For instance the default_security_group_id attribute of aws_vpc?

There may be a way to look up the group ID automatically? For instance the default_security_group_id attribute of aws_vpc?

Will OpenLMIS work with the latest version of postgres? Will this cause us to go up to that latest version?

Will OpenLMIS work with the latest version of postgres? Will this cause us to go up to that latest version?