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

Blackfire: tests, agent v2, separate agent package, blackfireio/integration-heroku buildpack support #488

Merged
merged 12 commits into from
Jun 25, 2021

Conversation

dzuelke
Copy link
Contributor

@dzuelke dzuelke commented Jun 25, 2021

Until now, the ext-blackfire extension also always bundled the blackfire-agent program. That program relays telemetry from a language runtime to the Blackfire servers in the background.

This PR:

dzuelke added 6 commits June 23, 2021 03:25
all env vars are shared between agent and extension, with the exception of the socket (BLACKFIRE_SOCKET vs BLACKFIRE_AGENT_SOCKET)

we are hard-coding the log file and agent socket values to ensure the basics always work; passing the socket directly to the agent
@dzuelke dzuelke requested a review from a team as a code owner June 25, 2021 15:02
@dzuelke dzuelke force-pushed the blackfire-agent-package branch from f638c49 to 79f4553 Compare June 25, 2021 15:13
@dzuelke dzuelke requested a review from schneems June 25, 2021 15:13
@dzuelke dzuelke merged commit 004442d into main Jun 25, 2021
@dzuelke dzuelke deleted the blackfire-agent-package branch June 25, 2021 15:36
@dzuelke dzuelke mentioned this pull request Jun 25, 2021
Copy link

@lolautruche lolautruche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you have the possibility to automatically download the latest version of Blackfire extension of needed?

@dzuelke
Copy link
Contributor Author

dzuelke commented Jun 25, 2021

We can't do that for compliance reasons, unfortunately - released versions must be fixed and mirrored by us for audit log purposes.

Longer-term, I guess the best solution is for us to simply not provide the CLI at all, but it'd be great if the user experience was reasonable in that case (i.e., meaningful error message instructing folks to install your buildpack).

Of course, another solution would be for you to also provide the extension packages ;) We can tackle that after I migrated the platform installer plugin to Composer v2.

@lolautruche
Copy link

OK understood.

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.

3 participants