influxdata / influxdata/iot-api-js
Troubleshooting suggests `grep INFLUX_TOKEN .env.local`, but `.claude/settings.json` denies `Read(./.env.*)`—an agent using Claude Code won’t be permitted to run read operations against `.env.local`. Either relax the deny rule (for non-secret `.env.development` at least) or adjust troubleshooting steps to avoid reading `.env.*` files.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 5
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 2
Description
Troubleshooting suggests `grep INFLUX_TOKEN .env.local`, but `.claude/settings.json` denies `Read(./.env.*)`—an agent using Claude Code won’t be permitted to run read operations against `.env.local`. Either relax the deny rule (for non-secret `.env.development` at least) or adjust troubleshooting steps to avoid reading `.env.*` files.
```suggestion
echo "INFLUX_TOKEN env var: ${INFLUX_TOKEN:-'(not set)'}"
```
_Originally posted by @Copilot in https://github.com/influxdata/iot-api-js/pull/29#discussion_r2789216260_
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 with the troubleshooting instructions and .claude/settings.json, then compare the suggested grep command with the denied Read(./.env.*) rule. Confirm the chosen approach works for an agent using Claude Code, and consider the issue done when the troubleshooting guidance and permission behavior no longer conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100