-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[cmd/opampsupervisor] Release Supervisor binary #24293
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
I'll determine an approach to this and update the issue in the next week or so. |
As discussed in the April 17 SIG meeting, we've agreed to publish this from the -releases repo. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
@evan-bradley should this be "never stale"? |
Component(s)
cmd/opampsupervisor
Is your feature request related to a problem? Please describe.
A Supervisor binary is currently not available for download anywhere. It needs to be made available to end users once it is considered ready for release.
Describe the solution you'd like
Release the Supervisor as a binary on GitHub. The supported architectures should match those of the Collector.
Open questions:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: