Feature request: Rebuild to later UCC version

[agiallombardo]

Description

Please create a way to rebuild and existing generated TA with the latest framework updates. Going back through to the init, build, package after a valid TA has been created is challenging. When merging files it's prone to errors and would love to take advantage of new UCC features on subsequent TA releases.

[hetangmodi-crest]

Hi @agiallombardo, usually the practices are that the globalConfig, app.manifest (updated as per the use cases of an add-on) and any other customizations required or functionalities that UCC doesn't provide at a given time, are persisted by an add-on developer on version control system.
However, in the current state, you can reuse the globalConfig present under the appserver directory as the source file and regenerate the add-on with any new use cases that you may have to add.
In a nutshell, the steps would look something like this:

1. Get the globalConfig from <add-on_package>/appserver/static/js/build of your already created add-on
2. Create a new directory and link it to a VCS
3. Put this globalConfig at the root level of this repository
4. Create a package directory
5. Copy the .conf files from your already created add-on to <your_repository>/package/default/
6. Add the files to your version control system
7. Build the add-on and test it on a Splunk instance.
8. Since now your source code is linked to a version control system, you wouldn't have to recreate the add-on from init, but rather from ucc-gen build for the new features you add in your add-on.

[agiallombardo]

@hetangmodi-crest Thank you, that's a good idea. The next request would be to create a feature that 'upgrade' in-place and is aware of any Python, JS, HTML, etc. changes that need to be made to be compatible/fix with the new version.