forked from open-telemetry/opentelemetry-collector-contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
/
support-extrat-parameters-to-be-compatible-with-minio.yaml
executable file
·29 lines (23 loc) · 1.49 KB
/
support-extrat-parameters-to-be-compatible-with-minio.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# Use this changelog template to create an entry for release notes.
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: enhancement
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
component: awss3exporter
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: "add support for `s3_force_path_style` and `disable_ssl` parameters"
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
issues: [ 29331 ]
# (Optional) One or more lines of additional information to render under the primary note.
# These lines will be padded with 2 spaces and then inserted directly into the document.
# Use pipe (|) for multiline entries.
subtext: |
In order to support alternative object-storage, these parameters are useful and help to leverage those systems not
compatible with domain style path, or just hosted without ssl (like just deployed in a k8s namespace).
# If your change doesn't affect end users or the exported elements of any package,
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
# Optional: The change log or logs in which this entry should be included.
# e.g. '[user]' or '[user, api]'
# Include 'user' if the change is relevant to end users.
# Include 'api' if there is a change to a library API.
# Default: '[user]'
change_logs: [ user ]