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
I'm in the process of updating an Ansible playbook I haven't touched in a year and I'm now getting validation errors about my role metadata requiring a galaxy_info.license value. These roles are being used privately and, as such, aren't licensed. I went through the list of licenses defined in the schema and couldn't find anything that corresponds to private, non-licensed code (not to be confused with "unlicensed" code).
Setting the license field to be null seems to me to be a more accurate representation of my role's licensed status, but the schema disallows that. For now, I'm just setting the value to an empty string. There isn't any validation of the field contents, which is nice, but what's the recommended way of dealing with this situation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm in the process of updating an Ansible playbook I haven't touched in a year and I'm now getting validation errors about my role metadata requiring a
galaxy_info.license
value. These roles are being used privately and, as such, aren't licensed. I went through the list of licenses defined in the schema and couldn't find anything that corresponds to private, non-licensed code (not to be confused with "unlicensed" code).Setting the
license
field to benull
seems to me to be a more accurate representation of my role's licensed status, but the schema disallows that. For now, I'm just setting the value to an empty string. There isn't any validation of the field contents, which is nice, but what's the recommended way of dealing with this situation?Beta Was this translation helpful? Give feedback.
All reactions