Skip to content

Opening up Fineract.dev Error Reporting to trusted committers #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vorburger opened this issue Dec 28, 2021 · 10 comments
Closed

Opening up Fineract.dev Error Reporting to trusted committers #9

vorburger opened this issue Dec 28, 2021 · 10 comments
Assignees

Comments

@vorburger
Copy link
Owner

Seeing @ptuomola fix https://github.com/apache/fineract/pull/1980/files for https://issues.apache.org/jira/browse/FINERACT-1089 reminded me of the general https://issues.apache.org/jira/browse/FINERACT-932, and I had an idea / suggestion / proposal:

@ptuomola, or anyone else reading along here, would you have any interest in being able to have view access to (only) the Error Reporting for Fineract.dev on the Google Cloud Console? Would you have any interest in occassionally checking it out? I believe it may be possible for me to set this up with a few clicks.

BTW if interested, what is your view about just making this completely publicly accessible, or just to some (Google, not Fineract) logins? My initial thought here is that security wise it's perhaps not a great idea to expose logs to anyone, unauthenticated. Even if Fineract.dev is just a demo instance, I'm not entirely comfortable to completely open up the console. (If it's even possible on Google Cloud; I have not looked at the details of how to do this, yet.)

@vorburger vorburger self-assigned this Dec 28, 2021
@vorburger
Copy link
Owner Author

@ptuomola I have gone ahead and tried out a first related configuration ("IAM"); if I did it correctly, you should now be able to view https://console.cloud.google.com/errors?&project=vorburger-learn-appengin (if you login with your personal Google account on which we have emailed in the past). Check it out and let me know if that works or if I missed something (and if you want to keep it or prefer having this removed again, for any reason).

completely open up the console. (If it's even possible on Google Cloud; I have not looked at the details of how to do this, yet.)

It seems like it's not - at least there is no "open to the 'world' principal" (or no obvious one; I didn't search a lot).

@ptuomola
Copy link

ptuomola commented Dec 29, 2021 via email

@vorburger vorburger changed the title Opening up Fineract.dev Error Reporting to trusted committers, or even publicly? Opening up Fineract.dev Error Reporting to trusted committers Dec 29, 2021
@vorburger
Copy link
Owner Author

Cool. I've now also granted you "Cloud Build Viewer", so in addition to that Error Reporting you should be able to also see e.g. https://console.cloud.google.com/cloud-build/builds;region=global/e54a0a48-fbc0-44d6-b961-8d651b1ea972?project=vorburger-learn-appengin & Co. It occured to me that this may be handy and useful for you in the future as well.

Let me resolve this. I don't mind adding additional trusted committers to grant visiblity into Fineract.dev Error Reporting as needed - just ask, see 7de40df.

@jdailey
Copy link

jdailey commented Dec 30, 2021

Michael - maybe you could add me and anyone else on the Security list. That way, if there's a reported issue we can potentially reproduce it on dev and see in the log the result. It may be useful in some limited scenarios.

@vorburger
Copy link
Owner Author

maybe you could add me

done

@vorburger
Copy link
Owner Author

Cool. I've now also granted you "Cloud Build Viewer", so in addition to that Error Reporting you should be able to also see e.g. https://console.cloud.google.com/cloud-build/builds;region=global/e54a0a48-fbc0-44d6-b961-8d651b1ea972?project=vorburger-learn-appengin & Co. It occured to me that this may be handy and useful for you in the future as well.

FTR: This apparently did not quite work yet - I've just created new #10 to sort this out.

@vorburger
Copy link
Owner Author

@vidakovic @awasum if getting the same access would interest you as well, then please privately email me your Google (Gmail) Account ID.

@vorburger
Copy link
Owner Author

FTR @vidakovic also has access now.

@vorburger
Copy link
Owner Author

FTR @awasum also has access now.

@vorburger
Copy link
Owner Author

FTR @BLasan also has access now, based on interest in https://issues.apache.org/jira/browse/FINERACT-1266.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants