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

fix(kamel log): Use integration name for looking up containers #348

Merged
merged 1 commit into from
Jan 21, 2019

Conversation

rhuss
Copy link
Contributor

@rhuss rhuss commented Jan 21, 2019

Use integration name for looking up containers as a fallback if no
container could be found.

If no container could be identified even with the integration name,
use the first container for the log, assuming its the "main" container.

Fixes #347

@lburgazzoli
Copy link
Contributor

@rhuss seems ok, did you test against knative ?

labelSelector string
podScrapers sync.Map
counter uint64
}

// NewSelectorScraper creates a new SelectorScraper
func NewSelectorScraper(client kubernetes.Interface, namespace string, labelSelector string) *SelectorScraper {
func NewSelectorScraper(client kubernetes.Interface, namespace string, integrationName string, labelSelector string) *SelectorScraper {
Copy link
Contributor

Choose a reason for hiding this comment

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

if possible I would not use the name integration in this package

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, what's about defaultContainerName ?

Copy link
Contributor

Choose a reason for hiding this comment

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

fine with me

@rhuss
Copy link
Contributor Author

rhuss commented Jan 21, 2019

Yes, I have knative installed locally in minikube.

@rhuss
Copy link
Contributor Author

rhuss commented Jan 21, 2019

Le me fix the build issue.

@lburgazzoli
Copy link
Contributor

can you squash the commits ?

@rhuss
Copy link
Contributor Author

rhuss commented Jan 21, 2019

@lburgazzoli not sure about the build error. Seems to be unrelated to this PR ?

Use integration name for looking up containers as a fallback if no
container could be found.

If no container could be identified even with the integration name,
use the first container for the log, assuming its the "main" container.

Fixes apache#347
@lburgazzoli
Copy link
Contributor

looks like you need to rebase from master

@lburgazzoli lburgazzoli merged commit d3e646c into apache:master Jan 21, 2019
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