Remove public ingress alert issue URL routing#1404
Merged
Conversation
This was referenced Jun 18, 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
alert_issue_urlas a current public-ingress notification authority.alert_issue_urlduring filesystem/Postgres profile read migration.Refs #985
Refs #1322
Verification
uv run python -m unittest(2,764 tests): passed.uv run --extra dev ruff check .: passed.uv run --extra dev ruff format --check <changed files>: passed.uv run --extra dev mypy control_plane tests: passed.uv run launchplane service audit-config-authority --control-plane-root .: status ok; existing broad scanner findings unchanged/outside this slice.Notes
ruff format --check .still reports pre-existing unrelated formatting drift in 55 files; changed files are formatted.