feat: add UPF event and opt-in redirect rejection policy - #77
Merged
Alonza0314 merged 2 commits intoAug 19, 2026
Merged
Conversation
This was referenced Jun 21, 2026
1 task
haha39
force-pushed
the
feat/smf-event-exposure-openapi
branch
from
August 17, 2026 18:06
d357875 to
aa18223
Compare
Alonza0314
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR is rebuilt on top of
feat/releaseand uses its generator-producedsmf/EvtExposandupf/EvtExpospackages.It adds only the remaining functionality needed by the targeted SMF Event Exposure flow:
UPF_EVENTvalue inSmf_EvtExpos_SmfEvent;upf/EvtExpos.The generated Nupf Event Exposure models and Create/Delete operations are provided by
feat/releaseand are not duplicated or regenerated in this PR.Redirect behavior
Default redirect behavior remains unchanged for configurations that do not provide a redirect policy.
Callers may explicitly reject redirects with:
The policy is applied through a request-local
http.Clientvalue. It preserves the selected client's Transport, Timeout, Jar, and metrics behavior without mutating the original client, shared clients, or their transports.With redirect rejection enabled, generated Create and Delete operations receive the original
307or308response for normal response parsing. No request is sent to the redirect target, and a Create request body is not replayed.Tests
The added tests cover:
UPF_EVENTwire value;307and308responses;upf/EvtExposconfiguration opt-in;307and308;Validation
Validated locally with Go 1.26.2:
All commands passed.
gofmt -dreturned no output for the seven changed files, and the complete diff passedgit diff --check.The rebuilt head currently has no successful official CI result because the workflow run completed as
action_requiredwithout starting any jobs.Related