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

feat(ui/dataLoaders): Use env var for telegraf config auth token #11693

Merged
merged 1 commit into from
Feb 5, 2019

Conversation

ischolten
Copy link
Contributor

@ischolten ischolten commented Feb 5, 2019

Closes #11609

Briefly describe your proposed changes:
Rather than using the actual auth token for the telegraf config, the environmental variable $INFLUX_TOKEN will now get saved into the config.

  • Rebased/mergeable
  • Tests pass
  • Update Changelog
  • http/swagger.yml updated (if modified Go structs or API)
  • Sign CLA (if not already signed)

@ischolten ischolten force-pushed the feat/telegraf-auth-envvar branch from 454e663 to 26e2a15 Compare February 5, 2019 22:20
Copy link
Contributor

@OfTheDelmer OfTheDelmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just had a question related to another PR I had open

@@ -1,6 +1,7 @@
## v2.0.0-alpha.2 [unreleased]

## Features
1. [11693](https://github.com/influxdata/influxdb/pull/11693): Save the $INFLUX_TOKEN environmental variable in telegraf configs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice

@@ -299,7 +299,7 @@ export const createOrUpdateTelegrafConfigAsync = (authToken: string) => async (
type: TelegrafPluginOutputInfluxDBV2.TypeEnum.Output,
config: {
urls: ['http://127.0.0.1:9999'],
token: authToken,
token: '$INFLUX_TOKEN',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we won't store the exact token here anymore? Does that mean the auth token will need to be fetched separately for the TelegrafInstructionsOverlay in the other PR I've got open where it was using plugin.config.token?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yes i do believe that will affect the Instructions Overlay in that way. Since we are not going to store that anymore, fetching it will be the only to get that value.

@ischolten ischolten merged commit 14482cf into master Feb 5, 2019
@ischolten ischolten deleted the feat/telegraf-auth-envvar branch February 5, 2019 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants