You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible, but I don't think being able to completely change the tag name is a good idea. It can reduce clarity in both the deployed solution and make the props confusing as well. I'd like to know more about the policies before discussing a potential solution. Is the policy around prefixing tag names?
A prefix is one possible policy. You might also have users with specific naming conventions they want to apply, like maybe they want ScanStatus or SCAN_STATUS.
You could also have situations where there are multiple scanning tools in play, and we want to make it clear which tool is responsible for the tag, so something like clamav-scan-status or scan-status-clamav might be desired.
I don't really understand the concern about reducing clarity, but in any case, if you're not interested in adding the feature then go ahead and close it. I'll just arrange to change the tags when I move the object to the next bucket in the pipeline.
Some organisations have policies in place around allowed tag names, tag naming conventions, namespacing and such.
It would be handy to have the option to set the name of the "scan-status" tag, as a prop when deploying ServerlessClamscan.
The text was updated successfully, but these errors were encountered: