Skip to content
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

Pre-prod Tech Logs for TRV11 #1715

Open
wants to merge 44 commits into
base: main
Choose a base branch
from
Open

Conversation

dunowgithub
Copy link

Pre-prod Tech Logs for TRV11

Pre-prod Tech Logs for TRV11
Copy link

gitguardian bot commented Sep 27, 2024

⚠️ GitGuardian has uncovered 28 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
7620759 Triggered Generic High Entropy Secret 55a5810 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret a996508 TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret a95b13d TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret a996508 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret d062b5e TRV11/Miles_Kilometres/on_status.json View secret
7620759 Triggered Generic High Entropy Secret cf2f30e TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret 55a5810 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret a95b13d TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret cf2f30e TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret e375a49 TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret d062b5e TRV11/Miles_Kilometres/on_status.json View secret
7620759 Triggered Generic High Entropy Secret a95b13d TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret 9efa9e5 TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret b0e6a62 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret 9efa9e5 TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret 55a5810 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret a996508 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret 55a5810 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret a95b13d TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret a95b13d TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret a996508 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret a996508 TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret 55a5810 TRV11/Miles_Kilometres/Flow 1/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret a996508 TRV11/Miles_Kilometres/Flow 1/on_status.json View secret
7620759 Triggered Generic High Entropy Secret deb1b24 TRV11/Miles_Kilometres/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret deb1b24 TRV11/Miles_Kilometres/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret deb1b24 TRV11/Miles_Kilometres/on_confirm.json View secret
7620759 Triggered Generic High Entropy Secret d062b5e TRV11/Miles_Kilometres/on_status.json View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@dunowgithub
Copy link
Author

@sourabhsaini11 Submitting TRV11 Pre-Prod Logs for your review. Let us know if you need anything else.

@sourabhsaini11
Copy link

@dunowgithub, please submit /on_action calls and missing flows as well

@dunowgithub
Copy link
Author

sourabhsaini11 - Missing files have been uploaded. Please check

@sourabhsaini11
Copy link

@dunowgithub, please submit search_1 api pair call & seggregate calls on basis of flows as well

@dunowgithub
Copy link
Author

sourabhsaini11 - Done. Please have a look. You may please delete the files that are outside the "Flow" folder

@92shreyansh 92shreyansh added the TRV-11 Unreserved-Ticket label Oct 3, 2024
@sourabhsaini11
Copy link

@dunowgithub, please fix below issue
search

  • collected_by is missing in payments
  • bpp_uri & bpp_id is missing in context (for /search_2 only)

@dunowgithub
Copy link
Author

@dunowgithub, please fix below issue search

  • collected_by is missing in payments
  • bpp_uri & bpp_id is missing in context (for /search_2 only)

collected_by is missing in payments - This can be fixed
bpp_uri & bpp_id is missing in context (for /search_2 only) - Our Journey starts directly with Search_2. We cache the station codes and indicate that in START & END and wait for Sellers to respond. So we will NOT know bpp_i and bpp_uri. We will know only in on_search2 - So this should observation should be discarded.

@dunowgithub
Copy link
Author

@dunowgithub, please fix below issue search

  • collected_by is missing in payments
  • bpp_uri & bpp_id is missing in context (for /search_2 only)

Over to you..

#1) collected_by is missing in payments - FIXED
#2) bpp_uri & bpp_id is missing in context (for /search_2 only) - Our Journey starts directly with Search_2. We cache the station codes and indicate that in START & END and wait for Sellers to respond. So we will NOT know bpp_id and bpp_uri. We will know only in on_search2 - So this should observation should be discarded.

@sourabhsaini11
Copy link

@dunowgithub, please get below issues fixed as well
common_issue

  • tag SETTLEMENT_WINDOW value mismatch between /action & /on_action calls

search1

  • payment.collected_by is missing

confirm

  • bank_account_number & bank_code are mising in params

@dunowgithub
Copy link
Author

@dunowgithub, please get below issues fixed as well common_issue

  • tag SETTLEMENT_WINDOW value mismatch between /action & /on_action calls

search1

  • payment.collected_by is missing

confirm

  • bank_account_number & bank_code are mising in params

Hey,

We are committing to settlement to the seller in 3 days though the seller wants in 30 days. How is that a problem?

@dunowgithub
Copy link
Author

@dunowgithub, please get below issues fixed as well common_issue

  • tag SETTLEMENT_WINDOW value mismatch between /action & /on_action calls

search1

  • payment.collected_by is missing

confirm

  • bank_account_number & bank_code are mising in params

Hey,

We are committing to settlement to the seller in 3 days though the seller wants in 30 days. How is that a problem?

Whose bank_account_number & bank_code are mising in params?

@dunowgithub
Copy link
Author

@dunowgithub, please get below issues fixed as well common_issue

  • tag SETTLEMENT_WINDOW value mismatch between /action & /on_action calls

search1

  • payment.collected_by is missing

confirm

  • bank_account_number & bank_code are mising in params

#1) As long as our settlement window is lesser than that of the SELLER - I do not see any reason why this should be a show stopper - Let me know if you think otherwise

#2) search1 - We have provided the logs.

#3) Have added bank_account_number & bank_code as asked

Have submitted the following

search1/on_search1
search2/on_search2
init/on_init
confirm/on_confirm
status/on_status
cancel/on_cancel
cancel2/on_cancel2

@sourabhsaini11
Copy link

@dunowgithub, please fix the below issues
common_issue

  • tag SETTLEMENT_WINDOW value mismatch between /action & /on_action calls (what if BPP is asking P1D or PT1H as SETTLEMENT_WINDOW instead of P30D, will you guys still settle for P3D or agree to settle at their time-frame. Thus in such cases there's need to be clear terms defined in the contract or such discrepancy will occur)

on_confirm

  • fulfillments.id & payments.id mismatch between /on_init & /on_confirm

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

Successfully merging this pull request may close these issues.

3 participants