bug: telegraf configuration "listen for data" button submitting undefined org
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 117
- Forks
- 51
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 4
Description
Hitting the "listen for data" button on the "create a telegraf configuration" overlay in Cloud2 to test a telegraf connection can query an 'undefined' org, rather than the user's actual org id.
Cause appears to be that the redux state that identifies the user's bucket and org is not being populated into Redux.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Cloud2 "create a telegraf configuration" overlay and trace the "listen for data" button into the Redux state for the user's bucket and organization. Verify the request does not use an undefined organization and confirm it queries the user's actual organization when testing a Telegraf connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redux, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100