* feat: add the ability to replicate based on bucket name rather than bucket id.
- This adds compatibility with 1.x replication targets
* fix: improve error checking and add tests
* fix: add additional constraint to replications table
* fix: use OR not AND for constraint
* feat: delete invalid replications on downgrade
* fix: should be less than 2.4
* test: add test around down migration and cleanup migration code
* fix: use nil instead of platform.ID(1) for better consistency
* fix: fix tests
* fix: fix tests
* chore: fix build commands for new cross-builder
* fix: use xcc to determine compiler
* fix: use correct compiler for darwin tests
* fix: update perftest to 22.04 image
* fix: fix find dbrps, make bucket default if not overridden
* fix: allow filtering of virtual DBRPs, filter in shard mapper
* fix: update tests to mock for virtual filter for shards and update server test
* feat: Add the instance owner concept
* feat: improve handling of instance resource type
* fix: remove relic of cloud/oss split
* feat: Add an instance id. This gets set during onboarding and can be used to uniquely identify that instance.
* chore: Revert "feat: Add an instance id. This gets set during onboarding and can be used to uniquely identify that instance."
This reverts commit 6a712df61e.
We decided to stick with the "singleton" 1 id for now, as there is not a clear need for unique identifiers.
* chore: Update PULL_REQUEST_TEMPLATE.md
This is part of an initiative to disseminate PR-specific information for all PR stakeholders. In addition to reviewers, this information is needed by product and docs.
* chore: Update PULL_REQUEST_TEMPLATE.md
* chore: Apply suggestions from code review
Co-authored-by: Sam Arnold <sarnold@influxdata.com>
Co-authored-by: Jeffrey Smith II <jsmith@influxdata.com>
Co-authored-by: Sam Arnold <sarnold@influxdata.com>
Whilst working on cloud labels, I noticed that the label storage test
isn't correctly capturing the testScenario. This is because t.Parallel()
is in use, so only the "delete" scenario will only ever be tested.
The following changes fix that, by capturing the testScenario in a local
variable so that the test function can use that correctly.
As a drive-by, I fixed the error referencing the wrong expectation.
Filters that contain `or` may change between cursor resets so we must remember to update the condition in the read cursor.
```flux
|> filter(fn: (r) => ((r["_field"] == "field1" and r["_value"]==true) or (r["_field"] == "field2" and r["_value"] == false)))
```
Closes https://github.com/influxdata/flux/issues/4804
* build(flux): update flux to v0.173.0
* fix(fluxfmt): update tests for newline in Flux fmt
Flux fmt now explicitly adds a newline to the end of a file, updating
tests accordingly.
* feat: start work on remotes/replications phone home data
* feat: add remotes/replications phone home data (no tests
* refactor: use erroring binary conversions
* style: gofmt
* refactor: improve some error handling
* style: cleanup
* feat: add tests
* refactor: just list remotes/replications rather than decrement
* chore: linting fix
Co-authored-by: DStrand1 <dstrandboge@influxdata.com>
* build(flux): update flux to v0.171.0
* chore: remove testing.loadStorage from tests
Also update skip lists in Flux test harness
* chore: remove now redundant Go end-to-end unit tests
This testing is all now provided by the `fluxtest` harness.
* chore: update jsonparser to 1.1.1 and yaml.v3 to 3.0.1
Perform:
$ go mod edit -require github.com/buger/jsonparser@v1.1.1
$ go mod edit -require gopkg.in/yaml.v3@v3.0.1
$ go mod tidy
* chore(tests): adjust for whitespace in test output
Jeffrey Smith II
Sean Brickley
Andrew Lee
Brandon Pfeifer
Jonathan A. Sternberg
Christopher M. Wolff
Dane Strandboge
Ikko Ashimine
davidby-influx
Sam Dillard
Simon Richardson
Sunil Kartikey
Markus Westerlind
Nathaniel Cook
Guillaume Claret
Sam Arnold
Jeffrey Smith II
Jamie Strandboge