search

spotfiresoftware / spotfire-python

Package for Building Python Extensions to Spotfire®
Other
18 stars 6 forks source link

Make it easier to use the same requirements.txt file for analyst and server package SPKs #5

Closed bbassett-tibco closed 2 years ago

bbassett-tibco commented 3 years ago

It's common for customers to want to have the same set of Python packages bundled and distributed both on Analyst and on the Server, and they often get in trouble by trying to use the same requirements.txt file to build both. They then find that the SPKs replace each other when adding them to the deployment area since they end up with build with the same spkID.

Would be nice if we could detect, for example, that you're trying to build a server SPK with the same requirements.txt that was used for an Analyst SPK and either warn or automatically change the spkID. Or even better, allow a brand to include both builtIds for analyst and server so you can build both from the same requirements file.

Issue migrated from TIBCO Software JIRA [PYSRV-235] created by jorobert

bbassett-tibco commented 2 years ago

Support has been added to allow storing both analyst and server information in the requirement file's brand.

This support includes a new brand versioning attribute, and logic to automatically upgrade the brand to the new version. As a result, it's important to have the first build with this version to use the same --analyst command line flag (either being present or absent) as was used to build the package before. Failure to do so would cause the upgrade logic to assign the information to the wrong key in the new brand; it can be fixed by manually changing the key in the brand after the fact. This information will be added to the Spotfire product release notes when the next release of this repository is picked up by the Spotfire platform.