Option to export components/applications without secrets or team mappings

Currently when exporting a component/application from a DevOps Deploy server, the created file contains secrets and team mappings. These secrets and team mappings can prevent import of the file to another server for different reasons. The secrets require an encryption key from the server it was exported from to exist on the server the file is imported to, and the team mappings require that the exact set up of teams exists on the second server. Should one of these requirements not be met, then the import will fail.

The exported files can be manually edited in order to remove these references, however that has the inherent risk of accidently removing something that shouldn't be removed and thusly cause the file become corrupt instead. Additionally, even when removing the values for the secrets, during import to the second server the existing values in the components/applications are overridden by the empty values, requiring the previously existing secrets to be manually implemented once more after import is finished.

The idea is that having an option to export using only the general configuration and process setup without including secrets or team mappings will allow for a better way to create import "packages" for set ups using multiple DevOps Deploy servers.

For example:
An operations team has two servers. One for production with active users and one for internal testing by the operations team. The production server receives multiple changes to the configuration and processes due to user input, business requirements, and development, while the test server is only updated when a new version of a tool or software needs to be verified before being put on the production server. The test server is only meant to be a mirror of of the production server in its current state, and therefore a lot of changes could have been made to the production server depending on how often a verification needs to be done on the test server.

Having the encryption key from the production server kept on the test server isn't allowed for security reasons, and only the operations team is set up on the test server. Due to this, importing an exported component/application template from the production server fails due the exported secrets as well as no team mapping that matches and can only be completed by manually editing the file to not contain the encrypted values and none of the team mappings, which as previously stated runs the risk of making the file corrupt instead.

By having the option to specify whether or not secrets and team mappings are the included in the exported file, it will allow for a more effective way to manage multiple DevOps Deploy servers that are meant to have shared components/applications. Having to remove these references manually from each exported file is both ineffective and, as previously stated, has the risk of causing the file be corrupt due to manual handling.