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

storage controller: update binary name #70

Merged
merged 3 commits into from
Mar 7, 2024
Merged

storage controller: update binary name #70

merged 3 commits into from
Mar 7, 2024

Conversation

jcsp
Copy link
Contributor

@jcsp jcsp commented Mar 7, 2024

This is an update to reflect the changed name in neondatabase/neon#7042

Additionally update the readiness check settings to reflect that I have been using in deploys to eu-west-1, and set RUST_BACKTRACE (this is useful in case of panics)

@jcsp jcsp force-pushed the jcsp/update-binary branch from 8b6b660 to fa1a73a Compare March 7, 2024 11:50
@jcsp jcsp marked this pull request as ready for review March 7, 2024 11:52
@jcsp jcsp requested review from rahulinux and arpad-m and removed request for arpad-m March 7, 2024 12:37
jcsp added a commit to neondatabase/neon that referenced this pull request Mar 7, 2024
## Problem

The storage controller binary still has its historic
`attachment_service` name -- it will be painful to change this later
because we can't atomically update this repo and the helm charts used to
deploy.

Companion helm chart change:
neondatabase/helm-charts#70

## Summary of changes

- Change the name of the binary to `storage_controller`
- Skipping renaming things in the source right now: this is just to get
rid of the legacy name in external interfaces.

---------

Co-authored-by: Arpad Müller <[email protected]>
@jcsp jcsp merged commit 0bf5af2 into main Mar 7, 2024
3 checks passed
@jcsp jcsp deleted the jcsp/update-binary branch March 7, 2024 14:17
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