-
Notifications
You must be signed in to change notification settings - Fork 143
Update the auto YAML Generation #7725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
royendo
wants to merge
34
commits into
main
Choose a base branch
from
docs/auto-gen-YAML
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
34 commits
Select commit
Hold shift + click to select a range
1df036d
some changes for connector YAML
royendo 3ff888e
remove
royendo a381593
separated YAML schema
royendo b6b987f
nit
royendo d7d4b11
link fixes
royendo a3784a0
Update generate_project.go
royendo f2ed2c4
add sec warning
royendo d57d430
motherduck live connector
royendo e5434ee
remove local file from connector
royendo cd0c819
nit
royendo d3396eb
matching file names
royendo 16c99c6
reordered files and added sources YAML and model SQL
royendo 6ba0dcd
nit, fix links
royendo 4363fff
comparing with current YAML changes
royendo 64677e0
Merge branch 'main' into docs/auto-gen-YAML
royendo 77f0ca9
adding annotatons back
royendo 7c35559
gofmt, golint
royendo 0ff11e2
fix
royendo 11b2710
first pass fix, need to review a few other items
royendo db75a6b
remove toplevel driver
royendo 95ca49a
single project file
royendo 98baf56
Update generate_project.go
royendo 7065bcc
good old cursor wiped my functoni
royendo dba395a
missing parameters
royendo 6e32ddd
midding parameters and inline examples
royendo c55eff3
god so many false positives from asking cursor to merge files
royendo 6ffe7f8
adding links
royendo f69c89a
fixed oneOf
royendo 3b6517e
split data properties to have api excamples
royendo e67f159
gonig through files
royendo df54d71
returning original format
royendo f94396e
?
royendo c58c634
Merge remote-tracking branch 'origin/main' into docs/auto-gen-YAML
royendo e8c04e9
fixing urls,
royendo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
--- | ||
note: GENERATED. DO NOT EDIT. | ||
title: Alert YAML | ||
sidebar_position: 31 | ||
sidebar_position: 38 | ||
--- | ||
|
||
Along with alertings at the dashboard level and can be created via the UI, there might be more extensive alerting that you might want to develop and can be done so the an alert.yaml. When creating an alert via a YAML file, you'll see this denoted in the UI as `Created through code`. | ||
|
@@ -12,13 +12,15 @@ Along with alertings at the dashboard level and can be created via the UI, there | |
|
||
_[string]_ - Refers to the resource type and must be `alert` _(required)_ | ||
|
||
### `display_name` | ||
|
||
_[string]_ - Refers to the display name for the alert | ||
|
||
### `refresh` | ||
|
||
_[object]_ - Specifies the refresh schedule that Rill should follow to re-ingest and update the underlying data _(required)_ | ||
_[object]_ - Refresh schedule for the alert | ||
```yaml | ||
refresh: | ||
cron: "* * * * *" | ||
#every: "24h" | ||
``` | ||
_(required)_ | ||
|
||
- **`cron`** - _[string]_ - A cron expression that defines the execution schedule | ||
|
||
|
@@ -30,6 +32,14 @@ _[object]_ - Specifies the refresh schedule that Rill should follow to re-ingest | |
|
||
- **`run_in_dev`** - _[boolean]_ - If true, allows the schedule to run in development mode. | ||
|
||
### `display_name` | ||
|
||
_[string]_ - Display name for the alert | ||
|
||
### `description` | ||
|
||
_[string]_ - Description for the alert | ||
|
||
### `intervals` | ||
|
||
_[object]_ - define the interval of the alert to check | ||
|
@@ -42,15 +52,15 @@ _[object]_ - define the interval of the alert to check | |
|
||
### `watermark` | ||
|
||
_[string]_ - Specifies how the watermark is determined for incremental processing. Use 'trigger_time' to set it at runtime or 'inherit' to use the upstream model's watermark. | ||
_[string]_ - Specifies how the watermark is determined for incremental processing. Use 'trigger_time' to set it at runtime or 'inherit' to use the upstream model's watermark. | ||
|
||
### `timeout` | ||
|
||
_[string]_ - define the timeout of the alert in seconds (optional). | ||
|
||
### `data` | ||
|
||
_[oneOf]_ - Specifies one of the options to retrieve or compute the data used by alert _(required)_ | ||
_[oneOf]_ - Data source for the alert _(required)_ | ||
|
||
- **option 1** - _[object]_ - Executes a raw SQL query against the project's data models. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same here. we should not remove options. |
||
|
||
|
@@ -122,7 +132,7 @@ _[string]_ - Defines the re-notification interval for the alert (e.g., '10m','24 | |
|
||
### `notify` | ||
|
||
_[object]_ - Defines how and where to send notifications. At least one method (email or Slack) is required. _(required)_ | ||
_[object]_ - Notification configuration _(required)_ | ||
|
||
- **`email`** - _[object]_ - Send notifications via email. | ||
|
||
|
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.