AFAIK today you cannot have password for triggering the pipeline. IMHO it's also not safe to have a single password for a pipeline (which would eventually get shared across the organisation), instead have you looked at role based security <https://docs.gocd.io/17.5.0/configuration/dev_authorization.html#role-based-security> ?
On Wed, May 3, 2017 at 1:07 AM, Vamshi krishna <[email protected]> wrote: > Is there anyway or a plugin whenever a pipeline gets triggered it should > prompt popup for a password(credentials). There's a secret variable option > but we would like have more control over this pipeline. like for AWS > credentials if stored in environment variables any GoCD admin can trigger > this pipeline so the pipeline prompting for the credentials would be a way > to go. any suggestions ? > > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Ashwanth Kumar / ashwanthkumar.in -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
