Should still be able to build with "EncryptSensitiveWithUserKey"

[paschott]

I can build packages like this through the VS IDE without needing to populate "correct" values for the parameters. I should be able to build packages through the tool. I noticed that this wasn't a valid option for the encryption settings on build, though.

[o-o00o-o]

I agree. I get the error:

EXEC : error : Invalid Protection Level for Deployment Package: EncryptSensitiveWithUserKey.

I want DontSaveSensitive for the ispac but EncryptSensitiveWithUserKey for source code to allow developers frictionless testing against sources with passwords and to allow the use of "Manage Parameter Values" for sensitive parameters in project parameters.

These don't work in VS when the project is in "DontSaveSensitive" mode (if they did I wouldn't need this).

This then means that devs have to switch the project param to not sensitive for a period of time which is much less secure.

I would switch to SaveSensitiveWithPassword but this requires some extra password work to get the password into msbuild but also it seems that there are problems with 2017/2019 projects and this package.

Any idea why it isn't supported? If I'm setting to DontSaveSensitive why should the ssis-build tool care what it is coming from as it is going to have to drop any encrypted stuff anyway?

Of course I could write a pre-build action to copy the files and modify them - or do a fork - but it feels like this library isn't being updated by the contributors with 14 outstanding PR's.