Merge branch 'main' into rin/fixup-rabbitmq_peer_discovery_etcd-dialyze

rabbitmq · Oct 4, 2024 · cc4b8ca · cc4b8ca
2 parents c6fe551 + 5bc0bcd
commit cc4b8ca
Show file tree

Hide file tree

Showing 687 changed files with 23,376 additions and 9,239 deletions.
diff --git a/.github/DISCUSSION_TEMPLATE/ideas.yml b/.github/DISCUSSION_TEMPLATE/ideas.yml
@@ -0,0 +1,55 @@
+title: "[Suggestion] "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Before We Start
+
+        Please provide reasonably detailed responses to the question below to help the Core Team and maintainers
+        to understand how you run RabbitMQ and why you'd like to see the suggested changes.
+  - type: markdown
+    attributes:
+      value: |
+        ## Relevant Details
+  - type: dropdown
+    id: rabbitmq_series
+    attributes:
+      label: RabbitMQ series
+      options:
+        - 3.13.x
+        - 4.0.x
+        - 4.1.x
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: Operating system (distribution) used
+      description: What OS or distribution do you run RabbitMQ on?
+    validations:
+      required: true
+  - type: dropdown
+    id: deployment_type
+    attributes:
+      label: How is RabbitMQ deployed?
+      options:
+        - Community Docker image
+        - Debian package
+        - RPM package
+        - Generic binary package
+        - Kubernetes Operator(s) from Team RabbitMQ
+        - Bitnami Helm chart
+        - Chocolatey package
+        - Windows installer
+        - Windows binary package
+        - RabbitMQ-as-a-Service from a public cloud provider
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: What would you like to suggest for a future version of RabbitMQ?
+      description: Please take the time to explain how you use RabbitMQ and why this change is important
+    validations:
+      required: true
diff --git a/.github/DISCUSSION_TEMPLATE/other.yml b/.github/DISCUSSION_TEMPLATE/other.yml
@@ -0,0 +1,56 @@
+title: "[Other] "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Before We Start
+
+        This category exists for free form questions where deployment details are less relevant, e.g. application and topology
+        advice kind of questions. Please provide a reasonably detailed description of how you use RabbitMQ.
+  - type: checkboxes
+    attributes:
+      label: Community Support Policy
+      description:
+      options:
+        - label: I have read [RabbitMQ's Community Support Policy](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md)
+          required: true
+  - type: markdown
+    attributes:
+      value: |
+        ## Relevant Details
+  - type: dropdown
+    id: rabbitmq_version
+    attributes:
+      label: RabbitMQ version used
+      options:
+        - 4.0.2
+        - 3.13.7
+        - 3.13.6
+        - 3.12.x or older
+    validations:
+      required: true
+  - type: dropdown
+    id: deployment_type
+    attributes:
+      label: How is RabbitMQ deployed?
+      options:
+        - Community Docker image
+        - Debian package
+        - RPM package
+        - Generic binary package
+        - Kubernetes Operator(s) from Team RabbitMQ
+        - Bitnami Helm chart
+        - Chocolatey package
+        - Windows installer
+        - Windows binary package
+        - RabbitMQ-as-a-Service from a public cloud provider
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: Steps to reproduce the behavior in question
+      description: What specific steps need to be performed in order to reproduce this behavior? Why?
+    validations:
+      required: true
diff --git a/.github/DISCUSSION_TEMPLATE/questions.yml b/.github/DISCUSSION_TEMPLATE/questions.yml
@@ -0,0 +1,202 @@
+title: "[Questions] "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Before We Start
+
+        Please provide reasonably detailed responses to the question below to help others help you.
+
+        If you omit relevant information, those trying to reproduce what you are about to report will have to guess.
+        Guessing is a very time consuming, and therefore expensive, approach to troubleshooting distributed messaging infrastructure.
+  - type: checkboxes
+    attributes:
+      label: Community Support Policy
+      description:
+      options:
+        - label: I have read [RabbitMQ's Community Support Policy](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md)
+          required: true
+        - label: I agree to provide all relevant information (versions, logs, rabbitmq-diagnostics output, detailed reproduction steps)
+          required: true
+  - type: markdown
+    attributes:
+      value: |
+        ## Relevant Details
+  - type: dropdown
+    id: rabbitmq_version
+    attributes:
+      label: RabbitMQ version used
+      options:
+        - 4.0.2
+        - 3.13.7
+        - 3.13.6
+        - 3.12.x or older
+    validations:
+      required: true
+  - type: dropdown
+    id: erlang_version
+    attributes:
+      label: Erlang version used
+      options:
+        - 26.2.x
+        - 26.1.x
+        - 26.0.x
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: Operating system (distribution) used
+      description: What OS or distribution do you run RabbitMQ on?
+    validations:
+      required: true
+  - type: dropdown
+    id: deployment_type
+    attributes:
+      label: How is RabbitMQ deployed?
+      options:
+        - Community Docker image
+        - Debian package
+        - RPM package
+        - Generic binary package
+        - Kubernetes Operator(s) from Team RabbitMQ
+        - Bitnami Helm chart
+        - Chocolatey package
+        - Windows installer
+        - Windows binary package
+        - RabbitMQ-as-a-Service from a public cloud provider
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: diagnostics_status
+    attributes:
+      label: rabbitmq-diagnostics status output
+      value: |
+        See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
+        <details>
+
+        ```
+        # PASTE OUTPUT HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: true
+  - type: textarea
+    id: rabbitmq_logs
+    attributes:
+      label: Logs from node 1 (with sensitive values edited out)
+      description: Relevant RabbitMQ logs with sensitive values edited out
+      value: |
+        See https://www.rabbitmq.com/docs/logging to learn how to collect logs
+        <details>
+
+        ```
+        # PASTE LOG HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: true
+  - type: textarea
+    id: logs_node_2
+    attributes:
+      label: Logs from node 2 (if applicable, with sensitive values edited out)
+      description: Relevant RabbitMQ logs with sensitive values edited out
+      value: |
+        See https://www.rabbitmq.com/docs/logging to learn how to collect logs
+        <details>
+
+        ```
+        # PASTE LOG HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: false
+  - type: textarea
+    id: logs_node_3
+    attributes:
+      label: Logs from node 3 (if applicable, with sensitive values edited out)
+      description: Relevant RabbitMQ logs with sensitive values edited out
+      value: |
+        See https://www.rabbitmq.com/docs/logging to learn how to collect logs
+        <details>
+
+        ```
+        # PASTE LOG HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: false
+  - type: textarea
+    id: rabbitmq_conf
+    attributes:
+      label: rabbitmq.conf
+      description: rabbitmq.conf contents
+      value: |
+        See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location
+        <details>
+
+        ```
+        # PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: true
+  - type: textarea
+    id: deployment_steps
+    attributes:
+      label: Steps to deploy RabbitMQ cluster
+      description: How would you explain how you deploy RabbitMQ to a new colleague?
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction_steps
+    attributes:
+      label: Steps to reproduce the behavior in question
+      description: What specific steps need to be performed in order to reproduce this behavior? Why?
+    validations:
+      required: true
+  - type: textarea
+    id: advanced_config
+    attributes:
+      label: advanced.config
+      description: advanced.config contents (if applicable)
+      value: |
+        See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location
+        <details>
+
+        ```
+        # PASTE advanced.config HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: false
+  - type: textarea
+    id: app_code
+    attributes:
+      label: Application code
+      description: Relevant messaging-related parts of application code
+      value: |
+        <details>
+
+        ```python
+        # PASTE CODE HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: false
+  - type: textarea
+    id: k8s_deployment
+    attributes:
+      label: Kubernetes deployment file
+      description: Kubernetes deployment YAML that demonstrates how RabbitMQ is deployed (if applicable)
+      value: |
+        <details>
+
+        ```yaml
+        # Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
+        # PASTE YAML HERE, BETWEEN BACKTICKS
+        ```
+        </details>
+    validations:
+      required: false
diff --git a/.github/workflows/gazelle-scheduled.yaml b/.github/workflows/gazelle-scheduled.yaml
@@ -30,7 +30,7 @@ jobs:
       run: |
         bazel run gazelle
     - name: CREATE PULL REQUEST
-      uses: peter-evans/create-pull-request@v6.1.0
+      uses: peter-evans/create-pull-request@v7.0.5
       with:
         token: ${{ secrets.REPO_SCOPED_TOKEN }}
         committer: GitHub <noreply@github.com>

diff --git a/.github/workflows/gazelle.yaml b/.github/workflows/gazelle.yaml
@@ -25,7 +25,7 @@ jobs:
       run: |
         bazel run gazelle
     - name: CREATE PULL REQUEST
-      uses: peter-evans/create-pull-request@v6.1.0
+      uses: peter-evans/create-pull-request@v7.0.5
       with:
         token: ${{ secrets.REPO_SCOPED_TOKEN }}
         committer: GitHub <noreply@github.com>

diff --git a/.github/workflows/rabbitmq_peer_discovery_aws.yaml b/.github/workflows/rabbitmq_peer_discovery_aws.yaml
@@ -66,7 +66,7 @@ jobs:
         ecs-cli --version
     - name: AUTHENTICATE TO GOOGLE CLOUD
       if: steps.authorized.outputs.authorized == 'true'
-      uses: google-github-actions/auth@v2.1.3
+      uses: google-github-actions/auth@v2.1.6
       with:
         credentials_json: ${{ secrets.REMOTE_CACHE_CREDENTIALS_JSON }}
     - name: CONFIGURE BAZEL

diff --git a/.github/workflows/templates/test-mixed-versions.template.yaml b/.github/workflows/templates/test-mixed-versions.template.yaml
@@ -23,11 +23,8 @@ on:
   push:
     branches:
       - main
-      - v3.12.x
-      - v3.11.x
-      - v3.10.x
-      - v3.9.x
-      - v3.8.x
+      - v4.0.x
+      - v3.13.x
       - bump-otp-*
       - bump-elixir-*
       - bump-rbe-*
@@ -99,7 +96,7 @@ jobs:
           https://builds.hex.pm
           https://cdn.jsdelivr.net/hex
     - name: AUTHENTICATE TO GOOGLE CLOUD
-      uses: google-github-actions/auth@v2.1.3
+      uses: google-github-actions/auth@v2.1.6
       with:
         credentials_json: ${{ secrets.REMOTE_CACHE_CREDENTIALS_JSON }}
     - name: BUILD SECONDARY UMBRELLA ARCHIVE

diff --git a/.github/workflows/templates/test.template.yaml b/.github/workflows/templates/test.template.yaml
@@ -22,7 +22,8 @@ name: Test
 on:
   push:
     branches:
-      - main
+#!      - main
+      - v4.0.x
       - v3.13.x
       - v3.12.x
       - v3.11.x
@@ -41,7 +42,7 @@ on:
       - '*.bzl'
       - '*.bazel'
       - .github/workflows/test.yaml
-  pull_request:
+#!  pull_request:
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: true
@@ -72,7 +73,7 @@ jobs:
       run: |
         echo "value=bazel-repo-cache-${{ hashFiles('MODULE.bazel') }}" | tee -a $GITHUB_OUTPUT
     - name: AUTHENTICATE TO GOOGLE CLOUD
-      uses: google-github-actions/auth@v2.1.3
+      uses: google-github-actions/auth@v2.1.6
       with:
         credentials_json: ${{ secrets.REMOTE_CACHE_CREDENTIALS_JSON }}
     - name: REPO CACHE