Cloning project with a new user group
Article ID: 402936
Updated On:
Products
Issue/Introduction
Attempting to export a project using the hexpenv command, then re-import it using the himpenv command to create a clone of the project, the intended difference being that the cloned project will have new user groups assigned.
Command used to export the project:
hexpenv.exe -b [BROKER NAME] -en [PROJECT NAME] -f export.har -eh harvest-login.dfo -wts -o output-export.log
Command used to import the project:
himpenv.exe -b [BROKER NAME] -f import.har -eh harvest-login.dfo -wts -o output-import.log
Between commands, the har file "export.har" is modified with a text editor to switch out the existing values under the "nameUserGroup" parameter and is saved as "import.har"
Running the above results in no error on import in the himpenv log (file output-import.log), but the project is not cloned as intended.
Environment
Release: 14.5
Cause
Modifying the har file directly is unsupported. There are unsupported workarounds to modify the file as a means to "hack" the file, as a way to automate the project creation process. Broadcom Support does not recommend following such procedures
Resolution
The "eug" parameter for hexpenv and "iug" parameter for himpenv should also be included to account for the user groups
Additional Information
Feedback
