I did not check the command yet, but I think we don't check the ports to be unique:
zowe:
components:
something1:
enabled: true
port: 123
something2:
enabled: true
port: 123
something3:
enabled: false
port: 123
The bind test checks the given port, the example above can succeed, but there is a port conflict.
This conflict will be detected anyway, as the second (started) component will not be able to use such port.
This check should be easy to implement - it can cover a special situation, when the component is taken from defaults and user is not aware of that:
components:
gateway:
enabled: true
port: 7558 # <--- customized, gateway is usually 7554 in our examples, but why not
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# zaas not defined here in config, but defined in defaults with port 7558
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
zaas: |
|
enabled: true |
|
port: 7558 |
|
debug: false |
I did not check the command yet, but I think we don't check the ports to be unique:
The bind test checks the given port, the example above can succeed, but there is a port conflict.
This conflict will be detected anyway, as the second (started) component will not be able to use such port.
This check should be easy to implement - it can cover a special situation, when the component is taken from defaults and user is not aware of that:
zowe-install-packaging/files/defaults.yaml
Lines 206 to 209 in cdeace0