influxdata / influxdata/influxdb
Open up to run e2e tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Use case:__
When doing e2e testing of application it is of great interest to be able to run a valid version of the server locally or be able to wipe data from buckets to be able to start from nothing each test session.
__Proposal:__
Want to be able to delete data from a bucket without having to remove the entire bucket and create one again. This is since I want the access token only to have access to the specific test bucket.
__Current behaviour:__
Currently not possible and doing e2e test the way I want is impossible.
__Desired behaviour:__
To be able to delete data.
__Alternatives considered:__
1. Release docker images of what is running as serverless 3.x.
2. Having access tokens that are able to create buckets and only delete buckets that the token it self has created.
Contributor guide
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
The issue names no file, test, or entry point. Start by locating the bucket data-deletion and access-token authorization paths, then clarify the intended deletion scope and API behavior; done should include an isolated way to remove bucket data without deleting the bucket and coverage for the stated token restriction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100