I have the following scenario:
I have a 2012 SSIS project that contains two packages and on the release of the project, I deploy the entire project solution which has both packages. I then create a SQL Agent job that executes the packages from the SSIS catalog and all is well.
Down the road, a change is required for both packages and both packages are being developed. The first package change is ready to be deployed and the business wants the change to be implemented and does not want to wait for the second package development.
How do I deploy my project to get the first package deployed without overwriting the second package? I do not want to drop out the second package from the project because the agent job is depending on the package to be located in the catalog. However, I cannot just create a new project deployment with the second package changes since the second package is not ready to be deployed yet.
Is this possible? In the deployment wizard, nothing is available to select only a specific package to update.
I want to take advantage of the SSIS catalog for configuring connections, parameters and the like but this ability to replace a single package needs to be available.
Can we do something in Powershell to add the updated package to the packages collection, which will overwrite the existing package or would that mess up the project deployment and the OOTB versioning that exists?
Or, is the workaround to create a new project with the Package One Updates and the original Package Two, walk through the deployment wizard to create the ISPAC file and then deploy that project to the catalog. (I guess answering my own question here but really hoping for something more elegant)
Thanks in advance
Chuck