The architecture is discussed in issue https://github.com/Altinn/altinn-pdf/issues/16, but in short it's based on the app calling a PDF microservice providing it with a URL in the app. The PDF microservice calls back to the app using the provided URL, reads the generated HTML and converts it to PDF which is returned to the app.
The new PDF-generator is based on a container defined by browserless.io. The container will be running in the application owner Apps k8-cluster. To secure the container as much as possible it is being made unavailable from outside the k8-cluster.
Scope
All work related to the PDF-generator changes is split between two teams, which has organized their work in two epics. This epic focus on the technical part of turning HTML into a PDF. The other epic (https://github.com/Altinn/app-lib-dotnet/issues/63) is focused on generating the HTML.
We're postponing all worries related to PDF-A support to a future issue. This allows us to continue the work with browseless.io image without the need for any extra tooling like Ghostscript. This will also give us time to reassess the need for PDF/A.
Description
This epic is part of the roadmap issue https://github.com/Altinn/altinn-roadmap/issues/38 which is a rewrite of today's PDF generator.
Solution as of now
The architecture is discussed in issue https://github.com/Altinn/altinn-pdf/issues/16, but in short it's based on the app calling a PDF microservice providing it with a URL in the app. The PDF microservice calls back to the app using the provided URL, reads the generated HTML and converts it to PDF which is returned to the app.
The new PDF-generator is based on a container defined by browserless.io. The container will be running in the application owner Apps k8-cluster. To secure the container as much as possible it is being made unavailable from outside the k8-cluster.
Scope
All work related to the PDF-generator changes is split between two teams, which has organized their work in two epics. This epic focus on the technical part of turning HTML into a PDF. The other epic (https://github.com/Altinn/app-lib-dotnet/issues/63) is focused on generating the HTML.
We're postponing all worries related to PDF-A support to a future issue. This allows us to continue the work with browseless.io image without the need for any extra tooling like Ghostscript. This will also give us time to reassess the need for PDF/A.
Related and historic issues
16
21
Remaining work
34
44
45
43