Closed samualblair closed 2 months ago
Hey @samualblair, I think we have this in the latest round of fast templates. I will be working on the next release to include these soon
I confirmed that we are parsing the details from the ns configs and through the ns2fast mutations. Final step is to update fast templates to read those new params, which as indicated in the last comment, will be updated for the next release
Is your feature request related to a problem? Please describe. Currently, when AS3 Conversions are run, the service Port (port associated with a pool member) is not created in the AS3 file. This seems to be the situation for all conversions, so not specific to any NS configuration, always occurs.
This generally should be available in the source NS.conf file, and when not found for a given pool member I would expect this could be assumed to be the same as the virtual port used (LB Port used).
It is worth noting that in the VS Code Generator Screen for 'Fast Template' the Service port does show as present, so perhaps this is a FAST template issue?
Describe the solution you'd like It would be good to have NS.conf parsed and input into AS3 file with this information. Not sure of current cause, but assume it is one of: 1) Failed/Lack of parsing 2) Failed/Lack of mapping 3) Limitation of FAST template
Describe alternatives you've considered For now, workarounds are to manually verify and add, or use external scripting tools to parse and add.
Additional context
Source NS.conf file has information such as:
An AS3 conversion ends up with pool section looking something like:
When it should look more like this (note servicePort):