influxdata/influxdb-action — explained in plain English
Analysis updated 2026-08-10 · repo last pushed 2024-05-31
Spin up a real InfluxDB database inside GitHub Actions to run automated tests against time-series data.
Test an IoT app that stores sensor readings by writing and reading data from a temporary InfluxDB instance during CI.
Install only the InfluxDB command-line tools in your workflow without starting the database server.
Pin a specific InfluxDB version in CI to match your production database for consistent test results.
| influxdata/influxdb-action | crokily/herdr-lazygit | davorpa/shell-utils | |
|---|---|---|---|
| Stars | 7 | 7 | 7 |
| Language | Shell | Shell | Shell |
| Last pushed | 2024-05-31 | — | 2021-09-18 |
| Maintenance | Dormant | — | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 2/5 | 1/5 |
| Audience | developer | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Just add the action to a GitHub Actions workflow YAML with a few parameters like version, org, username, password, and bucket name.
InfluxDB Action is a tool for developers who use GitHub Actions and want to spin up a temporary InfluxDB database as part of their automated testing. InfluxDB is a database designed for time-stamped data, like sensor readings or server metrics. Instead of manually installing and configuring a database every time you run a test, this action handles it for you automatically. When you add this action to a GitHub Actions workflow, it downloads, installs, and configures a fresh instance of InfluxDB on the fly. You tell it which version of the database to use and provide some basic setup details like an organization name, a username, a password, and a data "bucket." The action then makes the database commands available to your workflow, so your tests can read and write data to a real database without you needing to set one up yourself. This is useful for teams building applications that interact with time-series data. For example, if you are building an app that stores temperature readings from IoT devices, you want to make sure your code correctly saves and retrieves that data. By dropping this action into your testing pipeline, your automated tests can run against a real InfluxDB instance every time you commit code. You can also use it to install just the command-line tools without actually starting the database, if all you need is the CLI. One handy detail is that you can pin a specific version of the database, or grab the latest or nightly release. This means you can run your tests against the exact same database version your app uses in production, or experiment with upcoming features. The README doesn't go into deeper detail on advanced configuration, but it covers the essentials for getting a database running in a CI environment.
A GitHub Actions tool that automatically spins up a temporary InfluxDB time-series database in your CI pipeline so your tests can run against a real database without manual setup.
Mainly Shell. The stack also includes Shell, GitHub Actions, InfluxDB.
Dormant — no commits in 2+ years (last push 2024-05-31).
No license information is provided in the README, so usage rights are unclear.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.