-
Notifications
You must be signed in to change notification settings - Fork 3
Description
We'd like to release this app on Splunkbase as a direct download rather than as an "externally hosted" app. Splunk doesn't allow us to just convert an existing app between these types, therefore we need to upload a new app.
Additionally, Splunk now frowns upon reusing an existing sourcetype name that ships with Splunk enterprise, see #10. So we have to change the sourcetype postfix_syslog to something new. At the moment, I'm assuming that we also have to update the app id (folder name) to something new as well.
We would move the existing "master" branch to a new branch representing the "NEW" version of the app, the existing branch would be kept for some time for anyone still on the older version. Each branch would have some clear instructions in the README explaining the situation (and linking to the other), and there would be some "upgrade" notes on how to migrate from the legacy version to the updated and Splunkbase-available version.
Here's what I'm thinking in terms of renaming stuff. Please provide feedback with any recommendations or gotchas.
| Name | Current value | New app (SplunkBase) | Old app (git-only) |
|---|---|---|---|
| App id | TA-postifx |
TA-postfix2 * |
TA-postfix |
| App version | 0.8.x | 2.x.x * | 0.8. |
| Splunkbase id | 3347 | TBD * | 3347 |
| Label | Postfix Add-on for Splunk | Postfix Add-on for Splunk | Postfix Add-on for Splunk (Legacy) * |
| Sourcetype | postfix_syslog | mail:postfix * | postfix_syslog |
| Git branch | master | main * | legacy * |
Where * indicates a change.