@akhilmhdh wrt the commented out block in secret-service.ts, using the cli secrets set command, where in this case the secret key already exists, instead of updating the existing secret with the new value it always gave this response
error: CallUpdateSecretsV3: Unsuccessful response. Please make sure your secret path, workspace and environment name are all correct [response={"statusCode":400,"message":"Secret already exist","error":"BadRequest"}]
Unable to process secret update request
Commenting out that block resolves it. Is it by design or its a bug?
Closes #1612 @maidul98
@akhilmhdh wrt the commented out block in
secret-service.ts
, using the cli secrets set command, where in this case the secret key already exists, instead of updating the existing secret with the new value it always gave this responseCommenting out that block resolves it. Is it by design or its a bug?