Previously the build phase would only install the invoker once. After this,
if /workspace/.invoker directory was found, it would just assume the invoker
was already there and skip it.
A case where this could be a problem is if the invoker has been updated in
the buildpack. Functions that have previously been built will skip installation
of the new invoker.
This change modifies the behavior so that the invoker itself is always installed.
This is no problem with build time. It just copies two files. Then the
package-lock.json checksum is used to determine if there has been a change,
and if so, run npm ci again.
Previously the build phase would only install the invoker once. After this, if /workspace/.invoker directory was found, it would just assume the invoker was already there and skip it.
A case where this could be a problem is if the invoker has been updated in the buildpack. Functions that have previously been built will skip installation of the new invoker.
This change modifies the behavior so that the invoker itself is always installed. This is no problem with build time. It just copies two files. Then the package-lock.json checksum is used to determine if there has been a change, and if so, run npm ci again.
Signed-off-by: Lance Ball lball@redhat.com