DO NOT MERGE - Per Tenant Logging Testing

[shaangill025]

No description provided.

[esune]

@shaangill025 the permission error we are seeing when creating the log file in OpenShift could be resolved by having the logs go into /home/aries/log rather than in /home/aries, as that folder should have the right privileges set for the user to write to it.
We probably want to have this applied as default folder in ACA-Py, rather than leaving it to the user.

[shaangill025]

@esune I made the change in the following commit to allow --log-file to be applied to the logging handler if already created from config. So --log-file ./log/acapy.log would work with new pre-release image. Earlier the path specified in the config [ini] file could not be override. Regarding putting ./log/.. as the default path in ACA-Py, I am not sure if this is the way to go as this would work within Traction env but not if ACA-Py [multitenant] is stood up by itself. Currently the hang up is with the caplog issue with unit tests as I had mentioned in my updates today.
openwallet-foundation/acapy@c46c4d0

[esune]

@esune I made the change in the following commit to allow --log-file to be applied to the logging handler if already created from config. So --log-file ./log/acapy.log would work with new pre-release image. Earlier the path specified in the config [ini] file could not be override. Regarding putting ./log/.. as the default path in ACA-Py, I am not sure if this is the way to go as this would work within Traction env but not if ACA-Py [multitenant] is stood up by itself. Currently the hang up is with the caplog issue with unit tests as I had mentioned in my updates today. hyperledger/aries-cloudagent-python@c46c4d0

Thank you @shaangill025, i think I follow now. Looping in @WadeBarnes for potential input/insight on the operations end.

[WadeBarnes]

For anyone using the ACA-Py images the ./log folder is where logs are expected to be written if stored to disk.

[swcurran]

@WadeBarnes — are you now happy with the implementation in ACA-Py? As in approving the PR?

@shaangill025 — two of the test Actions are failing in the ACA-Py PR. Could you please investigate and address them? We’ve had some trouble with the JSON-LD tests failing to resolve a URL that could be the cause of the integration test errors (or not…), but that would not be the issue with the other failing action.

[WadeBarnes]

@WadeBarnes — are you now happy with the implementation in ACA-Py? As in approving the PR?

I've been letting @esune lead on the review of the Per Tenant Logging. I'm just commenting on the default location used for ACA-Py when it logs to disk. The images setup a ./log (more precisely a ~/log) folder and relevant permissions for this purpose, but the defaults in ACA-Py seem to log to files in the . (more precisely the ~) folder.

[WadeBarnes]

The pods associated with this PR are still in a crash loop.
cc @shaangill025, @esune, @i5okie

[github-actions]

Deployment	Resource	Location
Traction
	Tenant UI	https://pr-875-traction-tenant-ui-dev.apps.silver.devops.gov.bc.ca
	Innkeeper UI	https://pr-875-traction-tenant-ui-dev.apps.silver.devops.gov.bc.ca/innkeeper
Aca-Py
	Admin Swagger	https://pr-875-traction-acapy-admin-dev.apps.silver.devops.gov.bc.ca/api/doc
	Tenant Proxy Swagger	https://pr-875-traction-tenant-proxy-dev.apps.silver.devops.gov.bc.ca/api/doc

Deployment URLs ready for review.

[esune]

@shaangill025 do we need to do more testing on this or are we good since the changes were incorporated in ACA-Py and we can therefore close the PR?

[shaangill025]

We can close this PR as the associated changes are already merged in ACA-Py.