Hi @Rishi_Raj_Singh,
Thank you for your reponse.
Could it be modified to allow the user choose to only create asset but not override previously created assets?
i.e., The CI pipeline only creates assets (all type of assets) and does not override asset values. As I noted, CI pipelines can trigger many times. Our .csv file contains credential assets as well and the deploy function deploys / ovewrites on the already created asset, this is not good when we have credential asset.
For example lets say our asset.csv contains a credential asset type with a dummy password (to avoid freetext passwords in git repos). The Manage Asset Stage, creates the credential asset with a dummy value for the password. Later the developer updates the credential asset in Orchestrator (sets the correct password).
The deploy function currently keeps overwriting our credential asset with the dummy credential password. So wecannot use this stage in our CI.
If the deploy function has a choice where we can choose to avoid overwriting assets for credential assets.
Alternatively, the deploy function can work as it does now, but we avoid adding credential type asset in our asset.csv file.
Ayesha_Ijaz
baoutah999