Pipeline input to handle sensitive value
long-term
T
Tawny Aardvark
For some pipeline, we would like to be able to take sensitive value as input.
There's no easy way to do this at the moment.
Workaround is to create a secret resource, then tie the secret id to the pipeline... but this is clunky as it does not support parallel run and user have to update secret value prior to running pipeline.
Log In
M
Mantis Jellyfish
Hello Team,
We need to have a Harness pipeline where the user inputs the secret name and secret value, with the goal of creating a secret in GCP Secret Manager using the provided name and value/version. The secret value should not be stored or displayed in the pipeline console output or logs. However, in Harness, the available variable types are String, Secret, and Number. The Secret type only allows referencing secrets that are already stored in Harness or another integrated secret manager.
Please let me thoughts on this.
Prasad Satam
Merged in a post:
Possibility to enter password text value with masking the value when i am entering value as run time input.
P
Pleasant Moth
Possibility to enter password text value with masking the value when i am entering value as run time input.
We want to above use case achieved as can't use secret as the text password which i am entering is very dynamic, so every time its not passible to save the password and use it secret variable, and anywhere we dont use that password again.
Prasad Satam
updated the status to
long-term
Rohan Gupta
updated the status to
under review
A
Aquamarine Firefly
This is one the requirements we just gather from the developers too.