[jbosstools-issues] [JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23352 at 11/4/16 10:01 AM: -------------------------------------------------------------------- We maybe also should get rid of the add/remove/edit ports capability. See the discussion here: https://issues.jboss.org/browse/JBIDE-23368?focusedCommentId=13317423&... {quote} This was originally added because even though an image metadata does not indicate an image will be listening on a port, it still could be. For example, a debug port is open but I did not explicitly declare it in the dockerfile. Adding still allows you to configure a service that will expose the port. However, Andre Dietisheim and I had a long discussion about this issue and I believe we agreed on doing one of the following: * Remove the functionality all together to be consistent with the web ui * Modify button desc, add text to explain the ramifications, update the table to make it obvious these ports are not exposed I'm not certain what the right direction is other then we should probably follow the web and console as examples. You could always make the argument that a user can manually edit a service if an image does not explicitly expose ports. This seems reasonable to me. {quote} was (Author: adietish): We maybe also should get rid of the add/remove/edit ports capability. See the discussion here: https://issues.jboss.org/browse/JBIDE-23368?focusedCommentId=13317423&... {quote} This was originally added because even though an image metadata does not indicate an image will be listening on a port, it still could be. For example, a debug port is open but I did not explicitly declare it in the dockerfile. Adding still allows you to configure a service that will expose the port. However, Andre Dietisheim and I had a long discussion about this issue and I believe we agreed on doing one of the following: * Remove the functionality all together to be consistent with the web ui * Modify button desc, add text to explain the ramifications, update the table to make it obvious these ports are not exposed I'm not certain what the right direction is other then we should probably follow the web and console as examples. You could always make the argument that a user can manually edit a service if an image does not explicitly expose ports. This seems reasonable to me. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)