List all Labels
Retrieve a label by ID
Create a Label
Update a Label
Delete a Label
Add examples and test
Add necessary models
Signed-off-by: jeivardan <jeivardanvenkatesh@gmail.com>
- Check if database has default user, org, bucket
- Set up initial user, org and bucket
- Set up a new user, org and bucket
- Add examples and test
- Add necessary models
Signed-off-by: Aakash Hemadri <aakashhemadri123@gmail.com>
Get the readiness of an instance at startup
Signed-off-by: Aakash Hemadri <aakashhemadri123@gmail.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
* fix: influxdb2_client: enable rt-multi-thread
* fix: influxdb2_client: enable reqwest tls
Remove `default-features = false`. The default features of reqwest
enable "default-tls" which is required for support of https transport.
* fix: test_helpers crate should only be a dev-dep
* fix: object_store no longer has a build script, so no longer needs a build dep
* chore: Alphabetize all Cargo.tomls
* chore: Update arrow + tokio deps
* chore: Use bleeding edge azure
* chore: Update aws + other deps
* fix: fmt
* fix: Switch to in-house version of routerify
* fix: Upgrade to hyper 0.14
The hyper::error module is now private; hyper::Error is the public
re-export
* fix: Upgrade cloud storage to get tokio upgrade
* fix: Upgrade open_telemetry
* fix: Do not call `panic::set_hook` during another panic
Doing so leads to a double panic which aborts the process.
* fix: new h2 error who dis
Co-authored-by: Carol (Nichols || Goulding) <carol.nichols@integer32.com>
Co-authored-by: Jake Goulding <jake.goulding@integer32.com>
In the data generator, we're going to have potentially 2 different
clients for the data and for telemetry, and I'd like to be able to log
how they're configured, for example.
I don't see any reason for URL to
be private, because the user of the client passed in the URL and we
haven't changed anything about it.
Connects to influxdata/fusion#60
As far as I can tell, `/api/v2/write` uses `org` and `bucket` params
that can take org and bucket names, so just call those `org` and
`bucket` throughout and clarify in examples they can be any string.
However, `/api/v2/buckets` uses only `orgID` that must be the
organization's 16-digit hex ID, so clarify that case.
This means in examples where we create a bucket and push points into it,
we'll need both a hex ID and name for the organization.
Connects to influxdata/fusion#59. Delorean currently ignores this
header.
Also add an example of using this to connect to an InfluxDB 2 instance;
I tested this out with a locally running Influx DB 2 and I was able to
write points!
The `/api/v2/create_bucket` API was delorean-specific for testing
purposes. This change makes it match the [Influx 2.0 API][influx] and
adds a method to the client for creating buckets.
The client will always send an empty array of `retentionRules` because
that is a required parameter for the Influx API. Delorean always ignores
`retentionRules`. The `description` and `rp` parameters are optional and
are never sent.
[influx]: https://v2.docs.influxdata.com/v2.0/api/#operation/PostBuckets
I believe the gRPC create bucket is also delorean-specific and perhaps
not needed, but I'm leaving it in for now with a note.
jeivardan
Aakash Hemadri
Carol (Nichols || Goulding)
Andrew Lamb
Edd Robinson
Jake Swensen
Carol (Nichols || Goulding)
Dom
Jake Goulding