Skip to content

Conversation

mattmoor
Copy link
Contributor

This is a feature that's generally encouraged for consumers of GGCR, so that registry vendors can better identify the clients that are using GGCR to talk to registries.

cc @luhring

This is a feature that's generally encouraged for consumers of GGCR, so that registry vendors can better identify the clients that are using GGCR to talk to registries.

Signed-off-by: Matt Moore <mattmoor@chainguard.dev>
@jonjohnsonjr
Copy link
Contributor

Ideally you could include both os.Args[0] and the version, we do something similar for ggcr itself here: https://github.com/google/go-containerregistry/blob/098045d5e61ff426a61a0eecc19ad0c433cd35a9/pkg/v1/remote/transport/useragent.go#L23-L71

@mattmoor
Copy link
Contributor Author

Happy to include the version reflection logic if the maintainers want it, defer to them on preference.

@wagoodman
Copy link
Contributor

I think adding the application is a good start. If we're going to add version support that should probably be plumbed in via syft and grype directly (so expose a way to provide that via the API here).

@wagoodman wagoodman merged commit 410709c into anchore:main Mar 17, 2025
7 checks passed
@wagoodman wagoodman changed the title Set the GGCR user agent. Set the GGCR user agent Mar 17, 2025
@wagoodman wagoodman added the enhancement New feature or request label Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants