Validation inconsistency between the UI and API in work pool environment variables #12118
Closed
5 of 8 tasks
Comments
|
@zhen0 are you seeing this in the OSS UI? I may inadvertently provide a fix for this in https://github.com/PrefectHQ/nebula/pull/7083/commits/062a899d1e6675aa4e9c915d79a9e3f68c94ecb0 - I had to pull in some updates to our templating logic from OSS and that update specifically seems to affect environment variable resolution in templates. Let me check in on the fix once that commit is fully merged. |
|
This is no longer an issue I can produce. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First check
Bug summary
When editing a work pool from the UI it is possible to enter a boolean in the environment variable input. It is shown as valid json and accepted by the UI. However, the api rejects it and fails to save the work pool. From the network tab you can find the error "Validation failed for field 'env'. Failure reason: False is not of type 'object'"
Reproduction
Create a work pool
Enter 'True' or 'False' in the environment variables tab.
Try to save it.
Error
UI approves it as valid json.
Api retruns "Validation failed for field 'env'. Failure reason: False is not of type 'object'"
Browsers
Prefect version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: