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
As we extend the system to support different kinds of resources, the need to be able to trace the usage of those values becomes increasingly necessary. Today we have config and secrets, whose usage we are able to detect only when the handle itself is used in a verb. eg.
varsecret=ftl.Secret[string]("mySecret")
//ftl:exportfuncMyVerb(ctx context.Context, reqReq) (Resp, error) {
print(secret.Get()) // We can detect this usage.// ...
}
However if the secret value is retrieved at its global declaration point instead, we lose the ability to detect its usage:
varsecret=ftl.Secret[string]("mySecret").Get()
//ftl:exportfuncMyVerb(ctx context.Context, reqReq) (Resp, error) {
print(secret) // We can't detect this usage currently.// ...
}
This will become more important when we add support for PII data, and database field tracing.
The text was updated successfully, but these errors were encountered:
alecthomas
changed the title
Implement a general purpose data flow analyser for Go
Implement a general purpose data flow analyser for Go (and Kotlin)
Apr 12, 2024
As we extend the system to support different kinds of resources, the need to be able to trace the usage of those values becomes increasingly necessary. Today we have config and secrets, whose usage we are able to detect only when the handle itself is used in a verb. eg.
However if the secret value is retrieved at its global declaration point instead, we lose the ability to detect its usage:
This will become more important when we add support for PII data, and database field tracing.
The text was updated successfully, but these errors were encountered: