-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat: automatically generated instance_id #179
Conversation
scheduled_executor.thread.join | ||
|
||
Unleash.configuration.instance_id = original_instance_id | ||
Unleash.configuration.app_name = original_app_name |
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.
I don't think the property here really mattered for these tests (this should work with any property) so I picked app_name
instead.
Pull Request Test Coverage Report for Build 9841463298Details
💛 - Coveralls |
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.
Okaaaaay. I think this looks good but I wanna think a bit about what happens when your application gets forked by gunicorn or something equivalently horrible. I want to say that should be a new instance id
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.
We manually validated this together, I'm happy it works
https://linear.app/unleash/issue/2-2392/make-instance-id-autogenned-ruby
This makes
instance_id
an automatically generated read-only property, instead of being set by the user.Similar to Unleash/unleash-client-dotnet#226