If the ejson file and private env are not present, the hook would fail hard with exit 1 which is okay in most scenarios. However I am wondering if it is possible to introduce a flag to graceful exit 0 because in my case I am using one template for many pipelines and some of them do not bundle secrets.ejson file. I've been working around this by having a script to detect the presence of required params then adding or removing the ejson2env plugin accordingly (which is fine though a bit clunky IMHO).
cc @stevehodgkiss
If the ejson file and private env are not present, the hook would fail hard with
exit 1which is okay in most scenarios. However I am wondering if it is possible to introduce a flag to gracefulexit 0because in my case I am using one template for many pipelines and some of them do not bundle secrets.ejson file. I've been working around this by having a script to detect the presence of required params then adding or removing the ejson2env plugin accordingly (which is fine though a bit clunky IMHO).cc @stevehodgkiss