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

Update Starlark spec #10828

Closed
Hipska opened this issue Mar 16, 2022 · 0 comments · Fixed by #10940
Closed

Update Starlark spec #10828

Hipska opened this issue Mar 16, 2022 · 0 comments · Fixed by #10940
Labels
area/starlark dependencies Pull requests that update a dependency file docs Issues related to Telegraf documentation and configuration descriptions feature request Requests for new plugin and for new features to existing plugins

Comments

@Hipska
Copy link
Contributor

Hipska commented Mar 16, 2022

Feature Request

Please update starlark spec (module dependency) and make sure the docs link to the correct version of starlark used..

Current behavior:

Starlark README.md file links to the specs doc on master of starlark repository, while a specific older version is added/linked into telegraf.

Desired behavior:

Docs to point to matching spec documentation like: https://github.com/google/starlark-go/blob/7a1108eaa012/doc/spec.md

Use case:

Much easier to find available built-in functions based on your telegraf version.

@Hipska Hipska added feature request Requests for new plugin and for new features to existing plugins docs Issues related to Telegraf documentation and configuration descriptions area/starlark dependencies Pull requests that update a dependency file labels Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/starlark dependencies Pull requests that update a dependency file docs Issues related to Telegraf documentation and configuration descriptions feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant