drdelambre
commented
4 years ago here's the provisioning script we use internally for development, maybe we can add it to an entrypoint script?
#! /bin/bash
echo "Waiting for the api to spin up"
while [[ "$(curl -s --insecure -o /dev/null -w ''%{http_code}'' http://influxdb:9999)" != "200" ]]; do sleep 5; done
echo "Provisioning from environment variables"
curl -X POST -H "Content-type: application/json" \
-o ./auth-result.json \
-w "%{http_code}\n" \
-d "{\"username\":\"${INFLUX_USER}\",\"password\":\"${INFLUX_PASS}\",\"org\":\"${INFLUX_ORG}\",\"bucket\":\"${INFLUX_BUCKET}\"}" \
http://influxdb:9999/api/v2/setup 2>/dev/null >> ./status_code
read -r CODE < ./status_code
read -r BODY < ./auth-result.json
if [[ $CODE =~ ^20 ]]
then
TOKEN="$(jq -r .auth.token <<< $BODY)"
echo "export INFLUX_TOKEN=${TOKEN}" > /conf/influx-token.env
else
echo "already provisioned"
fi
jsternberg
bozic
skapin
Edo78
timhallinflux
loganmc10
w4tsn
agolovenko
Pierre-Lannoy
alsargent
tilchl
danxmoran
Proposal:
Can we get official 2.0 beta Docker images released to DockerHub?
Current behavior:
We currently release official Docker images on DockerHub for 1.x (https://hub.docker.com/_/influxdb). In addition to running influxdb, these images also allow for automatic creation of a database and a number of users. There are no such images available for 2.0 beta.
Desired behavior:
Have similar images for 2.0 beta as we do for 1.x, including the ability to easily provision an org, bucket, and user. In addition, because 2.0 requires a token for API requests, we'll need to come up with a secure way to make that token available for subsequent API calls after provisioning.
Alternatives considered:
We have "bare bones" images available at https://quay.io/repository/influxdb/influxdb?tag=latest&tab=tags, but they require additional work to provision. In addition, because 2.0 requires a token for making API calls, we need to come up with a solution for acquiring that token and making it available for subsequent API calls in a secure way.
There is v2 API endpoint for doing the provisioning at
/api/v2/setup(https://v2.docs.influxdata.com/v2.0/api/#operation/PostSetup) and it returns a JSON payload containing the token. Extracting this token from some kind of command-line utility requires additional tools likejq.Use case:
These images would be generally useful to allow people to get an instance of influxdb up and running quickly.
The particular use case I'm looking at right now is adding v2 support to the telemetry_influxdb project. This library is currently tested by spinning up a v1 Docker container using environment variables to provision a known DB and user/password. The tests then use those known values to run the library (which uses the
/writeAPI) and verify that it wrote the data correctly (using/query). See https://github.com/ludwikbukowski/telemetry_influxdb/blob/master/Makefile for how it runs the container.To test v2 similarly, we'd need a way to spin up a v2 container, provision it, and get access to the token so that we can run the library and verify its operations. We're currently using an image from
quay.ioas above, and then doing a bunch of extra work to provision, store the token, and make it available to the tests.This issue is somewhat related to #15761.