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

Dcoumentation error - 'Push Consumers' aka setting-up-consumer.rst - AWS_S3 example emphasizes wrong line #277

Open
samualblair opened this issue Apr 5, 2024 · 6 comments
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity

Comments

@samualblair
Copy link

Environment

N/A - Documentation bug.

Summary

This is due to error in documentation file:
docs/setting-up-consumer.rst

Additions to the AWS S3 consumer section.
Calls example file, but configured to highlight the wrong line.

.. literalinclude:: ../examples/declarations/consumers/AWS_S3/aws_s3.json
:language: json
:emphasize-lines: 12

Steps To Reproduce

Steps to reproduce the behavior:

  1. Submit the following declaration:

Browse to this page of documentation and view section on AWS S3.
https://clouddocs.f5.com/products/extensions/f5-telemetry-streaming/latest/setting-up-consumer.html

  1. Observe the wrong line highlighted.

Screenshot 2024-04-05 at 7 50 12 AM

Expected Behavior

The correct line (endpointURL) is highlighted.

Actual Behavior

The wrong line '{' is highlighted.

A Pull request has been created with fix for this:
#276

@samualblair samualblair added bug Something isn't working untriaged Issue needs to be reviewed for validity labels Apr 5, 2024
@samualblair
Copy link
Author

#276

@pgouband
Copy link

Hi @samualblair,

F5 Contributor License Agreement
Before you start contributing to any project sponsored by F5, Inc. (F5) on GitHub, you will need to sign a Contributor License Agreement (CLA).

If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.

If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.

If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.

@samualblair
Copy link
Author

Thanks, @pgouband, do you have any links or instructions for signing an F5 GitHub CLA?

I found some articles for OpenStack, Ansible, and others from various documentation pages. They all seem to be the same 'V1' document with different email groups. I have tried to send to the OpenStack email listed in the documents, but my emails get rejected for not being on an allowed list.

I'm trying Ansible email, so far that one hasn't been rejected yet, so maybe just the OpenStack email group has been shutdown/locked-down.

@zednickf5
Copy link

zednickf5 commented Jun 13, 2024

@samualblair please, email tele***.stream***@f5.com (*** expand to the whole word) to get CLA.

@samualblair
Copy link
Author

@samualblair please, email tele***.stream***@f5.com (*** expand to the whole word) to get CLA.

Thanks zednickf5, but I just keep getting undeliverable '503 #5.5.1 RCPT first (in reply to DATA command)' errors. I have tried from two different mail accounts, that don't seem to have problems sending messages otherwise. Are you sure that is a valid destination email?

The repo starts with f5, I also thought maybe f5.tele***.stream***@f5.com and f5tele***.stream***@f5.com , but same results with those.

@zednickf5
Copy link

Sorry @samualblair there was an issue with the email address. I've verified it works from external addresses. Please, try telemetry-streaming@...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity
Projects
None yet
Development

No branches or pull requests

3 participants