Closes https://github.com/influxdata/influxdb/issues/15060
Previously, the create button for a variable wouldn't be enabled unless
the user clicked in the text box, despite a query being present. This
adds an aditional check to the `isFormValid` method that ensures that if
a query is present the create button will be enabled.
The previous bucket retention form component was frusterating to use.
This commit replaces it with a simple duration dropdown that we use in a
few other places. It refactors the various duration utilities to make it
happen.
The hope is to eventually improve this duration dropdown into a combined
text input/dropdown component that can accept custom durations with
validation.
The following steps would result in a server error:
1. Open create bucket overlay
2. Enter valid name
2. Click "Periodically" radio option
3. Click "Never" again
4. Submit
The issue is that the bucket was being submitted with an invaild
retention duration, even though the user had selected to use no
retention duration (by clicking "Never").
The solution was to clear the retention duration state when switching
back to the "Never" radio option.
UpdateFlux is called during updates within the K/V store, and may
panic when parsing unexpected Flux scripts, which is undesirable.
We will look for an opportunity to log the panic, so they can be
tracked down and fixed.
* refactor(ui): remove action buttons from system bucket cards
* refactor(ui): make check builder more compact
* refactor(ui): add raw data toggle to check editor
* refactor(ui): fix logic for displaying system bucket label
* refactor(ui): remove edit link from system buckets
It was possible to create checks with invalid data causing
odd internal errors to return from the layers far down below.
Likely, we need to add more checks to the validation, but, I have
not thoroughly checked.
We want to display a row for each notification, but we were displaying
a row for each field for each notification.
By filtering out the system fields (those that start with an
underscore), we are in left with only a single user-specific field.
Closes https://github.com/influxdata/influxdb/issues/15042
Previously, there was an optional URL provided for the pagerduty
endpoint. However, the pagerduty API url does not change and as a result
it should not have been a parameter. The Pagerduty API does require a
`clientURL` that is presented in the pagerduty UI when an alert is
triggered. Currently that value will default to the alerts history page
for the organization.
* refactor(ui): add default values for deadman condition
* refactor(ui): limit values to 2 decimal places when dragging thereshold handles
* refactor(ui): prevent system buckets from being deleted or renamed
* refactor(ui): indicate which buckets are system buckets
* refactor(ui): prevent user from creating buckets starting with _
* refactor(ui): remove system bucketes from generate token overlay
* refactor(ui): remove system buckets from bucket dropdowns
* chore(ui): update changelog
Michael Desa
Christopher Henn
Lyon Hill
Jacob Marble
kelwang
Jakub Bednar
Alirie Gray
Stuart Carnie
Daniel Campbell
alexpaxton
Christopher M. Wolff
Chris Goller
Scott Anderson
Andrew Watkins
docmerlin (j. Emrys Landivar)
Kelvin Wang