Hi Team,
When releasing a new version of splunk add-on, is there a way to designate it as an optional upgrade? Is there a feature or best practice in Splunkbase or through add-on builder development methods that supports this distinction?
No, there isnt an option for this. The best thing to do here would be to put some detail in the release notes for the version - Splunk Admins *should* be checking release notes for apps they upgrade prior to upgrading them, therefore they should see that you have described it as an optional upgrade and thus can make a decision themselves on if to upgrade it or not.
Their justification on upgrading should usually be depending on compatibility, features, bugs and security fixes (for example) - if your new version of the app uses higher versions Splunk Python Libs for example then this might fall into the security fix category rather than new features - detailing this in the release notes will allow the admin to make the correct decision as to how important it is for them to do the upgrade.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing