Azure Functions triggers reveal secrets
SeanFeldman opened this issue · comments
@SeanFeldman thanks for bringing this to our attention. Will get digging into why that's happening.
Hey Sean thanks again for your time to raise this up as an issue. I know it's rather late to respond and I'm not sure if you're still using the extension but for this issue, you have to intentionally click the show value to reveal the sensitive data, correct?
Since that is the case I'm not sure the masking functionality is needed here. Could you possibly share more details on a scenario where this would still need to be masked after choosing to reveal the value?