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

Implement support for specifying container when getting logs #476

Closed

Conversation

johnksv
Copy link
Contributor

@johnksv johnksv commented Aug 26, 2024

If a pod have more than one container the current call will fail. This commit fix that issue, while preserving backward compatibility in the api by making the container id parameter optional.
The get logs call will behave as before if container id is null or empty.

This change may not make sense if there is no plan to implement support for this in the frontend (other changes may be required by api for this, such as returning which containers the pod contain).
If that is the case, feel free to close this PR

If a pod have more than one container the current call will fail. This
commit fix that issue, while perserving backward compability in the api
by making the container id parameter optional.
The get logs call will behave as before if container id is null or empty
Copy link

sonarcloud bot commented Aug 26, 2024

@johnksv
Copy link
Contributor Author

johnksv commented Aug 26, 2024

Closing as many changes are to come due to better pod detection

@johnksv johnksv closed this Aug 26, 2024
@johnksv johnksv deleted the get-logs-for-container branch August 26, 2024 13:02
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.

1 participant