This repository was archived by the owner on Jun 10, 2025. It is now read-only.
Log bamboo network requests in DB #1
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to help investigate a long running problem where Bamboo is changing the
employeeNumberthey have for a User on their end (this corresponds to a person's Pistachio User id.We are primarily interested in POST requests and for those we will also store the full log of the httparty debug of the request.
Merge Plan
Merge this PR while Pistachio ENV
BAMBOO_REQUEST_LOGGING_ENBALEDis not set and the Gem file is not updated to ref this commit.Merge https://github.com/alphasights/pistachio/pull/9280 with migration for
BambooRequestLogtable and updated gem file to ref thisNote
I have no idea why
tabular_data_update_rowbranch is used and notmasterin the Pistachio Gemfile