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

[Documentation/Event handler plugin] Clarification on the teleport.address attribute of the Helm chart #43181

Closed
elevesque-sfr opened this issue Jun 18, 2024 · 1 comment · Fixed by #48464

Comments

@elevesque-sfr
Copy link

Applies To

https://goteleport.com/docs/management/export-audit-events/fluentd/#step-66-run-the-event-handler-plugin
https://github.com/gravitational/teleport/blob/master/examples/chart/event-handler/README.md

Details

In the Teleport documentation, for the installation of the evnt handler plugin, at step 6/6, it says :

address: Include the hostname and HTTPS port of your Teleport Proxy Service or Teleport Enterprise Cloud tenant (e.g., teleport.example.com:443 or mytenant.teleport.sh:443).

In the README.md file in the repo github, it says :
teleport.address : Host/port combination of the teleport auth server

How will we know this is resolved?

What is the correct value of the attribute ? The proxy service or the auth service ?

Regards,
Eric

@ptgott

This comment has been minimized.

ptgott added a commit that referenced this issue Nov 5, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-merge-queue bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-actions bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-actions bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-actions bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-merge-queue bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-merge-queue bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
github-merge-queue bot pushed a commit that referenced this issue Nov 6, 2024
Closes #43181

Address inconsistent information between the Event Handler README and
step-by-step guides by using the information in the step-by-step guides,
which is more in line with our current recommendations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants