-
Notifications
You must be signed in to change notification settings - Fork 42
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
Migrate off storing BackendName
in Docker labels
#793
Migrate off storing BackendName
in Docker labels
#793
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Happy you were able to make plane work with just static labels!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but let's discuss before landing re. some other implications.
Instead of storing a label like: - "dev.plane.backend": "xjbgb03bhfxqgp" We will now store a label like: - "dev.plane.backend": "true" Critically, this allows us to continue relying on `"dev.plane.backend"` as an _identifier_ for plane backends, while deprecating the reliance on that label for carrying the `BackendName`. The only place we relied on the `BackendName` carried by this label was in the events loop, where as it turns out docker already applies a `"name"` attribute to events. Otherwise, introduce some helper functions to idiomatically convert between `ContainerId` and `BackendName`.
a34a08f
to
3ce9c9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the log collector fix.
Instead of storing a label like:
"dev.plane.backend"
:"xjbgb03bhfxqgp"
We will now store a label like:
"dev.plane.backend"
:"true"
Critically, this allows us to continue relying on
"dev.plane.backend"
as an identifier for plane backends, while deprecating the reliance on that label for carrying theBackendName
.The only place we relied on the
BackendName
carried by this label was in the events loop, where as it turns out docker already applies a"name"
attribute to events.Otherwise, introduce some helper functions to idiomatically convert between
ContainerId
andBackendName
.