Open kapilt opened 4 years ago
Thanks. We've added it to our backlog to look at in the future. Is this blocking you right now?
this feature is important for us as well.
re is it blocking, at scale.. i'd say its a basic platform miss and yes, function app cardinalities in 100s or 1000s (aka consumption which afaics is the only platform variant that aligns to serverless naming), not being able to have an exposed checksum is more problematic. even with async remote build and server side sync triggers it amounts to significantly of delays on idempotent deploy/update, plus extraneous log/audit trail events which need verification. re checksum simply exposing it on the upload artifact (aka the asset the user created) via rest api is ideal, in the world of kudu/webapps/functions mismatch (do functions even have an api?, why is kudu using timestamp checks + size instead of content for change detection).. currently looking at trying work around lack/platform by doing that client side via tags on fapps.
if a function hasn't changed, is it possible with func tools and kudu lite to effect a detection of no changes (md5 checksum?) and not perform the update/upload? linux consumption runtime v3.