|
1 | 1 | schema_version: 1
|
2 | 2 | name: eap
|
3 |
| -description: "Installs base EAP to the image" |
| 3 | +description: "Installs base EAP to the image." |
| 4 | + |
| 5 | +# NOTE: |
| 6 | +# The former listing of all specific EAP modules to be included into the RH-SSO |
| 7 | +# images was replaced with a single 'setup.eap.modules' CEKit module (therefore |
| 8 | +# one new layer in the resulting built container image). |
| 9 | +# |
| 10 | +# This single module combines / concatenates the functionality of all necessary |
| 11 | +# EAP modules, listed in the 'used-eap-modules-list.txt' in this directory, and |
| 12 | +# respects the internal dependencies between those modules. IOW the prerequisite |
| 13 | +# EAP modules are listed before the modules, which depend on them. |
| 14 | +# |
| 15 | +# This approach was chosen to avoid / overcome the 'max depth exceeded' OSBS |
| 16 | +# container build system error message, which got triggered previously by |
| 17 | +# performing an OSBS build, listing the necessary specific EAP modules |
| 18 | +# one-by-one. Due to the high number of EAP modules, needed to be included, |
| 19 | +# there were too many layers in the intermediary image, and the OSBS build |
| 20 | +# failed as a whole. |
| 21 | +# |
| 22 | +# IMPORTANT: |
| 23 | +# Do not change this approach! |
| 24 | +# |
| 25 | +# If you need to add / list additional EAP module, not present yet, append the |
| 26 | +# list of artifacts, environment variables, labels (basically all the |
| 27 | +# information listed in 'module.yaml' file of the new module, you want to add) |
| 28 | +# at the appropriate section of 'module.yaml' file of the existing |
| 29 | +# 'setup.eap.modules' module (for example append the labels from the new module |
| 30 | +# at the end of 'labels' section of 'setup.eap.modules' module, so the labels |
| 31 | +# from the new module are known to 'setup.eap.modules' module too. |
| 32 | +# |
| 33 | +# Moreover, copy the body of the configure script of that new module at the |
| 34 | +# appropriate place of the existing 'configure.sh' script. For each of the |
| 35 | +# already included configuration scripts, the 'configure.sh' script contains |
| 36 | +# the starting and ending comments, so the order in which the modules need |
| 37 | +# to be included, is preserved and respected. |
| 38 | + |
4 | 39 | version: '1.0'
|
5 | 40 |
|
6 | 41 | modules:
|
|
0 commit comments