[cloud][Canvas] Built asset removed in CI build

[clintandrewhall]

UPDATE:

I deployed the 7.5.0-SNAPSHOT to a Cloud instance, and the runtime is not present. I downloaded the built artifact and ran it locally: the file is present. It appears as though the Cloud process removes that file from its build of Kibana?

---

In #46278 I'm building a static runtime, kbn_canvas.js, in canvas/shareable_runtime/build. When I build Kibana locally, using yarn build, the file and its directory are present in the build directory. Further, the file and directory are present in the tar.gz file that results.

Yet the build file from CI does not contain that file and directory.

I assume the CI build is more representative of a production build than my local machine.

• Is there a build step or process I'm not following to reproduce this locally?
• Should I be whitelisting this path and file somewhere?
• Should I rename the directory?

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[clintandrewhall]

@spalger and @mistic helped me out with this -- confirmed fixed in the latest update to the PR. Thanks all!

[clintandrewhall]

This was fixed before I merged the PR. I just deployed the 7.5 SNAPSHOT and the runtime is not deployed in Cloud. Open to ideas.

[mieciu]

Just to leave a note after our debugging session with @kobelb . We had to comment out this check
of HapiJS which basically verifies whether kbn_canvas.js exists within confineDir.

If it doesn't (which turned out to be the case) handler.file() in here returns null and as a result 403 is thrown.

This probably indicates a mismatch between configuration of local dev setup and prod one we run in Cloud containers 🙂

[clintandrewhall]

#48663 Did not solve the problem. Opening a new PR.