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

Internal API - Visibility System support #1060

Merged
merged 7 commits into from
Dec 21, 2024

Conversation

eyalbe4
Copy link
Contributor

@eyalbe4 eyalbe4 commented Dec 20, 2024

This PR introduces an internal API, in the JFrog Platform, to allow for usage reporting for servies that rely on this library.

@eyalbe4 eyalbe4 added the improvement Automatically generated release notes label Dec 20, 2024
@eyalbe4 eyalbe4 added the safe to test Approve running integration tests on a pull request label Dec 20, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Dec 20, 2024
Copy link
Contributor

@sverdlov93 sverdlov93 left a comment

Choose a reason for hiding this comment

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

lets maybe explain above each usage manager whats it's purpose

jfconnect/manager.go Outdated Show resolved Hide resolved
jfconnect/services/metrics.go Outdated Show resolved Hide resolved
jfconnect/services/metrics.go Outdated Show resolved Hide resolved
jfconnect/services/metrics.go Outdated Show resolved Hide resolved
return *js.serviceDetails
}

func (js *JfConnectService) LogMetric(metric []byte) error {
Copy link
Contributor

Choose a reason for hiding this comment

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

metric has no type? just simple []byte?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it's just a JSON payload added to the post request.
Adding an additional type to that payload would add an unnecessary complication to the flow in my opinion.

@eyalbe4 eyalbe4 added the safe to test Approve running integration tests on a pull request label Dec 21, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Dec 21, 2024
@eyalbe4 eyalbe4 merged commit e5ef994 into jfrog:dev Dec 21, 2024
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Automatically generated release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants