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

PMM-13543 Support socket path. #961

Merged
merged 3 commits into from
Nov 14, 2024
Merged

Conversation

BupycHuk
Copy link
Member

@BupycHuk BupycHuk commented Nov 14, 2024

PMM-13477 Support of PSMDB 8.0.

PMM-13543 Support socket path.


Below we provide a basic checklist of things that would make it a good PR:

  • Make sure to sign the CLA (Contributor License Agreement).
  • Make sure all tests pass.
  • Keep current with the target branch and fix conflicts if necessary.
  • Update jira ticket description if necessary.
  • Attach screenshots and/or console output to the jira ticket to confirm new behavior, if applicable.
  • Leave notes to the reviewers if you need to focus their attention on something specific.

Once all checks pass and the code is ready for review, please add pmm-review-exporters team as the reviewer. That would assign people from the review team automatically. Report any issues on our Forum.

@BupycHuk BupycHuk requested a review from a team as a code owner November 14, 2024 09:21
@BupycHuk BupycHuk requested review from ademidoff and JiriCtvrtka and removed request for a team November 14, 2024 09:21
exporter/diagnostic_data_collector.go Outdated Show resolved Hide resolved
main.go Outdated Show resolved Hide resolved
@BupycHuk BupycHuk enabled auto-merge (squash) November 14, 2024 10:53
@BupycHuk BupycHuk merged commit dc46ed5 into main Nov 14, 2024
14 checks passed
@BupycHuk BupycHuk deleted the PMM-13543-support-socket-and-psmdb-8 branch November 14, 2024 10:56

// IF user@pass not contained in uri AND custom user and pass supplied in arguments
// DO concat a new uri with user and pass arguments value
if !strings.Contains(uri, "@") && user != "" && password != "" {
Copy link
Member

Choose a reason for hiding this comment

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

I'm wondering if we shouldn't support a case where the user is non-empty and the password is empty.

Copy link
Member Author

Choose a reason for hiding this comment

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

good point for improvement, but in scope of this fix I think we can leave as it used to be. I just reverted old logic for cases where url.Parse doesn't work. Additionally for that users can set user in initial DSN. let's create github issue with good-first-task label for those who would like to contribute

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