-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Flow variable import and data type fixes (#361)
* Draft fix * changelog * add better flow validation debug * add variable values validation * update documentation * switch flow read to export variable values * changelog * changelog * update tests * bump dv sdk * update for lint
- Loading branch information
1 parent
09dd805
commit 0b7885f
Showing
14 changed files
with
339 additions
and
114 deletions.
There are no files selected for viewing
This file contains 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 |
---|---|---|
@@ -0,0 +1,23 @@ | ||
```release-note:bug | ||
`resource/davinci_variable`: Fixed panic crash when attempting to create a new flow variable that does not already exist. | ||
``` | ||
|
||
```release-note:bug | ||
`resource/davinci_variable`: Fixed "Error reading variable: json: cannot unmarshal object into Go struct field" error on all variables when a flow sets a flow variable value to an object type. | ||
``` | ||
|
||
```release-note:breaking-change | ||
`resource/davinci_flow`: Reverted the ability to use flow exports with variable values removed. Variable values are required when importing flows using this provider. | ||
``` | ||
|
||
```release-note:bug | ||
`resource/davinci_flow`: Resolve warnings that state that DaVinci JSON files contain unknown properties when using flow variable nodes. | ||
``` | ||
|
||
```release-note:note | ||
`resource/davinci_flow`: Enhanced error messages that result from invalid flow formats. | ||
``` | ||
|
||
```release-note:note | ||
Bump `github.com/samir-gandhi/davinci-client-go` from 0.4.0 => 0.5.0 | ||
``` |
This file contains 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 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 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 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 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 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 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 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
Oops, something went wrong.