add logs tracking GCP secret fetch for NGINXaaS#1577
add logs tracking GCP secret fetch for NGINXaaS#1577vivki wants to merge 3 commits intonginx:mainfrom
Conversation
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1577 +/- ##
==========================================
- Coverage 85.02% 84.92% -0.10%
==========================================
Files 103 103
Lines 13589 13601 +12
==========================================
- Hits 11554 11551 -3
- Misses 1518 1535 +17
+ Partials 517 515 -2
... and 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
I have hereby read the F5 CLA and agree to its terms. |
7b3317d to
f00237a
Compare
|
recheck |
d5f9118 to
174dcf7
Compare
|
I have hereby read the F5 CLA and agree to its terms |
|
recheck |
e1c4663 to
e9c746e
Compare
| # Use PR head branch (the feature branch) when running from a pull_request event. | ||
| # Fallback to github.head_ref (sanity) or ref name for other contexts. | ||
| target-branch: ${{ github.event.pull_request.head.ref || github.head_ref || github.ref_name }} | ||
| # Use PR head SHA for pull requests (supports PRs from forks). |
There was a problem hiding this comment.
I'm not familiar with this repos workflows, so maybe someone from the agent team can take a look and see why this is necessary
05ea69e to
4948cf3
Compare
Use commit SHA instead of branch name when checking out PR code. This fixes the checkout error for PRs from forks where the branch doesn't exist in the upstream repository.
Proposed changes
This PR adds logs for external file downloads. These are needed on the NGINXaaS side to generate events.
Checklist
Before creating a PR, run through this checklist and mark each as complete.
CONTRIBUTINGdocumentmake install-toolsand have attached any dependency changes to this pull requestREADME.md)