community 
Distribute Blueprint and Resource Scripts with associated Metadata
This is a feature that is already present with shells. Shells can define their associated metadata via drivermetadata.xml
When distributing a resource script or blueprint level script it is a pain point for the admins that handle the upload to populate all this stuff manually in the GUI. Many times the admin doing the upload is not the same person that wrote the script. This upload misconfiguration leads to bugs. This places extra work on the developer to document all this metadata, and for the sys admin to properly add this manually.
The mechanism to define these fields should be in attached metadata files packaged with the scripts, similar to shells. This would also allow each script to be updated via api with its respective python version (currently will be uploaded as systems configured default python). An alternative is to add more parameters to the upload script api to set all this stuff (but I think a distributable package with metadata is cleaner, and just upload that via api without need for extra parameters)
The required data for scripts:
- script name
- script version
- python version
- visibility
- description
- attached models (for resource scripts only)
- categories
- alias
- parameters (and all the associated parameter metadata)
Thanks,
Natti
