add HTTP trigger download tips (#731)

Author: coco-super

lib/deploy/deploy-by-tpl.js

@@ -81,19 +81,14 @@ async function deployTriggers(serviceName, functionName, events) {
   let onLineTriggerNames = await getTriggerNameList({serviceName, functionName});
 
   onLineTriggerNames.filter(x =>!_.includes(localTriggerNames, x)).forEach(element => {
-
     console.warn(red(`\t\tThe trigger ${element} you configured in fc console does not match the local configuration.\n\t\tFun will not modify this trigger. You can remove this trigger manually through fc console if necessary`));
-
   });
 
   for (const [triggerName, triggerDefinition] of Object.entries(events)) {
     console.log(`\t\tWaiting for ${yellow(triggerDefinition.Type)} trigger ${triggerName} to be deployed...`);
-
     await deployTrigger(serviceName, functionName, triggerName, triggerDefinition);
-
     await displayTriggerInfo(serviceName, functionName, triggerName, triggerDefinition.Type, triggerDefinition.Properties, '\t\t');
-
-    console.log(green(`\t\tfunction ${triggerName} deploy success`));
+    console.log(green(`\t\ttrigger ${triggerName} deploy success`));
   }
 }
 

lib/trigger.js

@@ -434,7 +434,8 @@ async function displayTriggerInfo(serviceName, functionName, triggerName, trigge
       console.log(`${resolveWrap}triggerName: ${yellow(triggerName)}`);
     }
     console.log(`${resolveWrap}methods: ${yellow(methods)}`);
-    console.log(`${resolveWrap}url: ` + yellow(`https://${accountId}.${region}.fc.aliyuncs.com/2016-08-15/proxy/${serviceName}/${functionName}/\n`));
+    console.log(`${resolveWrap}url: ` + yellow(`https://${accountId}.${region}.fc.aliyuncs.com/2016-08-15/proxy/${serviceName}/${functionName}/`));
+    console.log(red(`${resolveWrap}Http Trigger will forcefully add a 'Content-Disposition: attachment' field to the response header, which cannot be overwritten \n${resolveWrap}and will cause the response to be downloaded as an attachment in the browser. This issue can be avoided by using CustomDomain.\n`));
   }
 }