We are a team working on a group of SSIS packages, which we share using version control (SVN) We do. We have three ways to save sensitive data in these packages:
- Do not store them at all
- user key Store with password
However, each of these options is inconvenient while other developers have been saved and committed packages tested is. For each such package, someone has to update the credentials, no matter how sensitive the data continues.
Is there a better way to collaborate on SSIS packages?
Uses file deployment since my workplace, I used "not saving sensitive" To make development easier, we also store the config files with packages in our version control system, and the connection string for the development environment is stored in config files. Config files are also stored in the named folder as well, so if I get the config files in my normal config file area, then I can open any of our project packages and they will work for me for development. When packages are deployed, then they are secured by the deployment team on the machine, where the developers do not have access and the config file value for connection strings is changed to match the production environment.
Comments
Post a Comment