You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Features: yaml bigfunctions files can now be nested in bigfunctions folder at any depth
Possible to have functions yaml files nested at any depth in folder hierarchy (it used to work for testing and deploying functions, it now also work for documentation website)
For this to work, Documentation structure has changed:
BEFORE: you had one /bigfunctions/ page listing all bigfunctions
NOW: you have one page per folder nested in bigfunctions folder such as /bigfunctions/transform/ /bigfunctions/transform/transform_string. Each folder is generated based on the README of the folder in which are added subfolders and bigfunctions exisiting in the folder
create_temp_dataset in python functions will give dataEditor role to function caller instead of custom bigfunctions role so that anyone can deploy it (useful for load_saas_data, etc)
fix quota management when only one of param is defined.
Features
when you put yaml type in function argument for a python function, it will be automatically parsed from string to object before the function code is executed