In order to apply the commercial license to PrinceXML, we need to be able to apply the license during the Lambda build stage. This pull request enables the license to applied where it's available, which at this time, is only in production.
Approach
In each environment, a default non-commercial license is applied that can be picked up while the function is being built. In production, the commercial license is available for the the production stage and the license will be applied while the function is built as part of the lambda layer.
Assorted Notes/Considerations
All environments must have the following SSM parameters applied with the non-commercial license:
/configuration/default/prince/license
Any environments that require the commercial license need to have the commercial license assigned to the appropriate SSM parameter:
/configuration/[branch_name]/prince/license
Purpose
In order to apply the commercial license to PrinceXML, we need to be able to apply the license during the Lambda build stage. This pull request enables the license to applied where it's available, which at this time, is only in production.
Approach
In each environment, a default non-commercial license is applied that can be picked up while the function is being built. In production, the commercial license is available for the the production stage and the license will be applied while the function is built as part of the lambda layer.
Assorted Notes/Considerations
All environments must have the following SSM parameters applied with the non-commercial license: /configuration/default/prince/license
License is as follows:
Any environments that require the commercial license need to have the commercial license assigned to the appropriate SSM parameter: /configuration/[branch_name]/prince/license