Remove the links to discord (#662)

* Remove the link to discord

Why: our discord has been sunset in favor of https://forums.percona.com

* chore: remove discord links

* ci: refactor some actions

* ci: refactor go.yml

Author: Alex Tymchuk

.github/pull_request_template.md

@@ -9,4 +9,4 @@
 - [ ] Update jira ticket description if needed.
 - [ ] Attach screenshots/console output to confirm new behavior to jira ticket, if applicable.
 
-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](https://forums.percona.com) or [Discord](https://per.co.na/discord).
+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](https://forums.percona.com).

.github/workflows/go.yml

@@ -3,7 +3,7 @@ name: Go
 on:
   schedule:
     # run every Sunday
-    - cron: "0 13 * * 0"
+    - cron: '0 13 * * 0'
   push:
     branches:
       - main
@@ -45,7 +45,7 @@ jobs:
     steps:
       - name: Set up Go release
         if: matrix.go-version != 'tip'
-        uses: percona-platform/setup-go@v2
+        uses: actions/setup-go@v4
         with:
           go-version: ${{ matrix.go-version }}
 
@@ -59,7 +59,7 @@ jobs:
           echo "$HOME/gotip/bin" >> $GITHUB_PATH
 
       - name: Check out code into the Go module directory
-        uses: percona-platform/checkout@v3
+        uses: actions/checkout@v3
 
       - name: Initialize dependencies and linters
         run: |

.github/workflows/release.yml

@@ -7,47 +7,43 @@ on:
       - v*
   # manually trigger the release
   workflow_dispatch:
+
 jobs:
   goreleaser:
     runs-on: ubuntu-latest
     steps:
-      -
-        name: Checkout
-        uses:  percona-platform/checkout@v3
+      - name: Checkout
+        uses: actions/checkout@v3
         with:
           fetch-depth: 0
-      -
-        name: Set up Go
-        uses: percona-platform/setup-go@v2
+
+      - name: Set up Go
+        uses: actions/setup-go@v4
         with:
           go-version: 1.19
-      -
-        name: Login to Docker Hub
-        uses: percona-platform/login-action@v2
+
+      - name: Login to Docker Hub
+        uses: docker/login-action@v2
         with:
           username: ${{ secrets.DOCKERHUB_USERNAME }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
-      -
-        name: Login to GitHub Container Registry
-        uses: percona-platform/login-action@v2
+      - name: Login to GitHub Container Registry
+        uses: docker/login-action@v2
         with:
           registry: ghcr.io
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
-      - 
-        name: Set up QEMU
+      - name: Set up QEMU
         uses: docker/setup-qemu-action@v2
 
-      - 
-        name: Set up Docker Buildx
+      - name: Set up Docker Buildx
         id: buildx
         uses: docker/setup-buildx-action@v2
 
-      -
-        name: Run GoReleaser
-        uses: percona-platform/goreleaser-action@v3
+      - name: Run GoReleaser
+        uses: goreleaser/goreleaser-action@v3
         with:
           version: latest
           args: release --rm-dist

.gitignore

@@ -6,3 +6,4 @@ bin
 build
 dist
 mongodb_exporter
+.DS_Store

CONTRIBUTING.md

@@ -22,7 +22,6 @@ If you find a bug in Percona MongoDB Exporter and it is not related to PMM, plea
 
 Your first step should be to search [GH issues](https://github.com/percona/mongodb_exporter/issues) and [JIRA PMM issues](https://jira.percona.com/issues/?jql=project=PMM%20AND%20component=MongoDB_Exporter) for the existing set of open tickets for a similar report. If you find that someone else has already reported your problem, then you can upvote that report to increase its visibility.
 
-
 ### Submitting PMM Bug
 
 If there is no existing PMM report for the issue that relates to PMM, submit a report following these steps:
@@ -35,13 +34,15 @@ An excellent resource is [Elika Etemad's article on filing good bug reports.](ht
 
 As a general rule of thumb, please try to create bug reports that are:
 
-- *Reproducible.* Include steps to reproduce the problem.
-- *Specific.* Include as much detail as possible: which version, what environment, etc.
-- *Unique.* Do not duplicate existing tickets.
-- *Scoped to a Single Bug.* One bug per report.
+- _Reproducible._ Include steps to reproduce the problem.
+- _Specific._ Include as much detail as possible: which version, what environment, etc.
+- _Unique._ Do not duplicate existing tickets.
+- _Scoped to a Single Bug._ One bug per report.
 
 ## Branching workflow
+
 MongoDB exporter uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html) `[major].[minor].[patch]`:
+
 - major version when you make incompatible changes
 - minor version when you add functionality in a backwards compatible manner
 - patch version when you make backwards compatible bug fixes
@@ -52,7 +53,6 @@ MongoDB exporter uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
 
 Each release is tagged with `vx.y.z` tag.
 
-
 Please submit your changes against `main` branch, if the fix is needed for the patch or minor release - please ask maintainers to cherry pick it into the release branch.
 
 ## Setup your local development environment
@@ -69,7 +69,7 @@ These are these available options:
 |format|Format source code|
 |check|Run checks/linters|
 |check-license|Check license in headers. |
-|help|Display this help message.  |
+|help|Display this help message. |
 |test|Run all tests (need to start the sandbox first)|
 |test-cluster|Starts MongoDB test cluster. Use `env var TEST_MONGODB_IMAGE` to set flavor and version. Example:|
 | |`TEST_MONGODB_IMAGE=mongo:3.6 make test-cluster`|
@@ -78,28 +78,32 @@ These are these available options:
 ### Initializing the development environment
 
 First you need to have `Go` and `Docker` installed on your system and then, in order to install tools to format, test and build the exporter, you need to run this command:
+
 ```
 make init
 ```
+
 It will install `goimports`, `goreleaser`, `golangci-lint` and `reviewdog`.
 
 ## Tests
 
 ### Starting the sandbox
 
 The testing sandbox starts `n` MongoDB instances as follows:
+
 - 3 Instances for shard 1 at ports 17001, 17002, 17003
 - 3 instances for shard 2 at ports 17004, 17005, 17006
 - 3 config servers at ports 17007, 17008, 17009
 - 1 mongos server at port 17000
 - 1 stand alone instance at port 27017
 
 All instances are currently running without user and password so for example, to connect to the **mongos** you can just use:
+
 ```
 mongo mongodb://127.0.0.1:17001/admin
 ```
-The sandbox can be started using the provided Makefile using: `make test-cluster` and it can be stopped using `make test-cluster-clean`.
 
+The sandbox can be started using the provided Makefile using: `make test-cluster` and it can be stopped using `make test-cluster-clean`.
 
 ### Running tests
 
@@ -120,4 +124,4 @@ After submitting your PR please add `pmm-review-exporters` team as a reviewer -
 
 Once your pull request is merged, you are an official Percona Community Contributor. Welcome to the community!
 
-We're looking forward to your contributions and hope to hear from you soon on our [Forums](https://forums.percona.com) and [Discord](https://discord.gg/mQEyGPkNbR).
+We're looking forward to your contributions and hope to hear from you soon on our [Forums](https://forums.percona.com).

README.md

@@ -4,7 +4,7 @@
 [![codecov.io Code Coverage](https://img.shields.io/codecov/c/github/percona/mongodb_exporter.svg?maxAge=2592000)](https://codecov.io/github/percona/mongodb_exporter?branch=main)
 [![Go Report Card](https://goreportcard.com/badge/github.com/percona/mongodb_exporter)](https://goreportcard.com/report/github.com/percona/mongodb_exporter)
 [![CLA assistant](https://cla-assistant.percona.com/readme/badge/percona/mongodb_exporter)](https://cla-assistant.percona.com/percona/mongodb_exporter)
-[![Discord](https://img.shields.io/discord/808660945513611334?style=flat)](http://per.co.na/discord)
+
 
 This is the new MongoDB exporter implementation that handles ALL metrics exposed by MongoDB monitoring commands.
 This new implementation loops over all the fields exposed in diagnostic commands and tries to get data from them.