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

storcon: add --control-plane-url config option #11173

Merged
merged 3 commits into from
Mar 12, 2025
Merged

Conversation

arpad-m
Copy link
Member

@arpad-m arpad-m commented Mar 11, 2025

Adds the --control-plane-url config option to the storcon, which we want to migrate to instead of using notify-attach.

Part of #11163

@arpad-m arpad-m requested a review from a team as a code owner March 11, 2025 14:23
@arpad-m arpad-m requested review from DimasKovas and arssher March 11, 2025 14:23
Copy link

github-actions bot commented Mar 11, 2025

7909 tests run: 7526 passed, 0 failed, 383 skipped (full report)


Flaky tests (1)

Postgres 17

Code coverage* (full report)

  • functions: 32.5% (8727 of 26874 functions)
  • lines: 48.4% (74648 of 154077 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
1b0a6a0 at 2025-03-12T00:03:48.473Z :recycle:

@arpad-m arpad-m added this pull request to the merge queue Mar 12, 2025
Merged via the queue into main with commit da2431f Mar 12, 2025
98 checks passed
@arpad-m arpad-m deleted the arpad/control_plane_url branch March 12, 2025 02:37
github-merge-queue bot pushed a commit that referenced this pull request Mar 13, 2025
We want to switch away from and deprecate the `--compute-hook-url` param
for the storcon in favour of `--control-plane-url` because it allows us
to construct urls with `notify-safekeepers`.

This PR switches the pytests and neon_local from a
`control_plane_compute_hook_api` to a new param named
`control_plane_hooks_api` which is supposed to point to the parent of
the `notify-attach` URL.

We still support reading the old url from disk to not be too disruptive
with existing deployments, but we just ignore it.

Also add docs for the `notify-safekeepers` upcall API.

Follow-up of #11173
Part of #11163
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants