minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-31 18:04:52 +03:00
Code Activity

correct NATS endpoint syntax (#1212)

Browse Source 
NATS endpoints should be specified with hostname and port, not a URL. 

Staged

http://192.241.195.202:9000/staging/nats-endpoint-fix/linux/reference/minio-server/settings/notifications/nats.html

http://192.241.195.202:9000/staging/nats-endpoint-fix/linux/administration/monitoring/publish-events-to-nats.html

Fixes https://github.com/miniohq/engineering/issues/1966
This commit is contained in:
Andrea Longo
2024-05-10 07:36:52 -06:00
committed by GitHub
parent 7013fc3723
commit 2953b54ecd
2 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
source/administration/monitoring/publish-events-to-nats.rst
View File

@ -79,8 +79,8 @@ You can configure a new NATS service endpoint using either environment variables
If the specified ``<IDENTIFIER>`` matches an existing NATS service endpoint on the MinIO deployment, the new settings *override* any existing settings for that endpoint. If the specified ``<IDENTIFIER>`` matches an existing NATS service endpoint on the MinIO deployment, the new settings *override* any existing settings for that endpoint.
Use :mc-cmd:`mc admin config get notify_nats <mc admin config get>` to review the currently configured NATS endpoints on the MinIO deployment. Use :mc-cmd:`mc admin config get notify_nats <mc admin config get>` to review the currently configured NATS endpoints on the MinIO deployment.
- Replace ``<ENDPOINT>`` with the URL of the NATS service endpoint. - Replace ``<ENDPOINT>`` with the hostname and port of the NATS service endpoint.
For example: ``htpps://nats-endpoint.example.com:4222`` For example: ``nats-endpoint.example.com:4222``
See :ref:`NATS Service for Bucket Notifications <minio-server-envvar-bucket-notification-nats>` for complete documentation on each environment variable. See :ref:`NATS Service for Bucket Notifications <minio-server-envvar-bucket-notification-nats>` for complete documentation on each environment variable.
@ -124,8 +124,8 @@ You can configure a new NATS service endpoint using either environment variables
If the specified ``IDENTIFIER`` matches an existing NATS service endpoint on the MinIO deployment, the new settings *override* any existing settings for that endpoint. If the specified ``IDENTIFIER`` matches an existing NATS service endpoint on the MinIO deployment, the new settings *override* any existing settings for that endpoint.
Use :mc-cmd:`mc admin config get notify_nats <mc admin config get>` to review the currently configured NATS endpoints on the MinIO deployment. Use :mc-cmd:`mc admin config get notify_nats <mc admin config get>` to review the currently configured NATS endpoints on the MinIO deployment.
- Replace ``ENDPOINT`` with the URL of the NATS service endpoint. - Replace ``ENDPOINT`` with the hostname and port of the NATS service endpoint.
For example: ``htpps://nats-endpoint.example.com:4222``. For example: ``nats-endpoint.example.com:4222``.
See :ref:`NATS Bucket Notification Configuration Settings <minio-server-config-bucket-notification-nats>` for complete documentation on each setting. See :ref:`NATS Bucket Notification Configuration Settings <minio-server-config-bucket-notification-nats>` for complete documentation on each setting.

12
source/reference/minio-server/settings/notifications/nats.rst
View File

@ -49,10 +49,10 @@ For example, the following commands set two distinct NATS service endpoints as `
:class: copyable :class: copyable
set MINIO_NOTIFY_NATS_ENABLE_PRIMARY="on" set MINIO_NOTIFY_NATS_ENABLE_PRIMARY="on"
set MINIO_NOTIFY_NATS_ADDRESS_PRIMARY="https://nats-endpoint.example.net:4222" set MINIO_NOTIFY_NATS_ADDRESS_PRIMARY="nats-endpoint.example.net:4222"
set MINIO_NOTIFY_NATS_ENABLE_SECONDARY="on" set MINIO_NOTIFY_NATS_ENABLE_SECONDARY="on"
set MINIO_NOTIFY_NATS_ADDRESS_SECONDARY="https://nats-endpoint.example.net:4222" set MINIO_NOTIFY_NATS_ADDRESS_SECONDARY="nats-endpoint.example.net:4222"
With these settings, :envvar:`MINIO_NOTIFY_NATS_ENABLE_PRIMARY <MINIO_NOTIFY_NATS_ENABLE>` indicates the environment variable is associated to an NATS service endpoint with ID of ``PRIMARY``. With these settings, :envvar:`MINIO_NOTIFY_NATS_ENABLE_PRIMARY <MINIO_NOTIFY_NATS_ENABLE>` indicates the environment variable is associated to an NATS service endpoint with ID of ``PRIMARY``.
@ -62,12 +62,12 @@ For example, the following commands set two distinct NATS service endpoints as `
.. code-block:: shell .. code-block:: shell
mc admin config set notify_nats:primary \ mc admin config set notify_nats:primary \
address="https://nats-endpoint.example.com:4222" \ address="nats-endpoint.example.com:4222" \
subject="minioevents" \ subject="minioevents" \
[ARGUMENT=VALUE ...] [ARGUMENT=VALUE ...]
mc admin config set notify_nats:secondary \ mc admin config set notify_nats:secondary \
address="https://nats-endpoint.example.com:4222" \ address="nats-endpoint.example.com:4222" \
subject="minioevents" \ subject="minioevents" \
[ARGUMENT=VALUE ...] [ARGUMENT=VALUE ...]
@ -105,7 +105,7 @@ Enable
:class: copyable :class: copyable
mc admin config set notify_nats \ mc admin config set notify_nats \
address="https://nats-endpoint.example.com:4222" \ address="nats-endpoint.example.com:4222" \
subject="minioevents" \ subject="minioevents" \
[ARGUMENT="VALUE"] ... \ [ARGUMENT="VALUE"] ... \
@ -128,7 +128,7 @@ Address
:delimiter: " " :delimiter: " "
Specify the NATS service endpoint to which MinIO publishes bucket events. Specify the NATS service endpoint to which MinIO publishes bucket events.
For example, ``https://nats-endpoint.example.com:4222``. For example, ``nats-endpoint.example.com:4222``.
.. include:: /includes/linux/minio-server.rst .. include:: /includes/linux/minio-server.rst
:start-after: start-notify-target-online-desc :start-after: start-notify-target-online-desc