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
json is the foundation of all the declarations we use on F5 products and the foundation of data exchange for everything we are doing going forward
Other technology vendors, like Ansible/TeraForm/docker/... all utilize yaml for its ease of use and visually easier to manage
yaml to json is a simple conversion already handled within the extension
If we simplify the file type to just (.as3/.do/.ts/.cs/.fast/... or even just .f5), we should be able to allow users to develop declarations as json OR YAML, and utilize any and all features of either language, including schema validation.
The extension would detect yaml vs json and convert yaml to json as part of the api call as needed.
Essentially, the extension could start the process of allowing users to build declarations in yaml and abstracting the process of converting to json before posting to the device
Need to figure out how other applications like FAST/Ansible/TF/... consume yaml information or if the post body already being converted to json as part of the http payload. This would help figure out how much effort it would be to support yaml in completeness, meaning, when the final files are integrated into an automated solution how is yaml consumed and passed to the end service (if/when it is converted to json at any point).
The text was updated successfully, but these errors were encountered:
json is the foundation of all the declarations we use on F5 products and the foundation of data exchange for everything we are doing going forward
Other technology vendors, like Ansible/TeraForm/docker/... all utilize yaml for its ease of use and visually easier to manage
yaml to json is a simple conversion already handled within the extension
If we simplify the file type to just (.as3/.do/.ts/.cs/.fast/... or even just .f5), we should be able to allow users to develop declarations as json OR YAML, and utilize any and all features of either language, including schema validation.
The extension would detect yaml vs json and convert yaml to json as part of the api call as needed.
Essentially, the extension could start the process of allowing users to build declarations in yaml and abstracting the process of converting to json before posting to the device
Need to figure out how other applications like FAST/Ansible/TF/... consume yaml information or if the post body already being converted to json as part of the http payload. This would help figure out how much effort it would be to support yaml in completeness, meaning, when the final files are integrated into an automated solution how is yaml consumed and passed to the end service (if/when it is converted to json at any point).
The text was updated successfully, but these errors were encountered: