After transitioning our project to Ruby 2.4 we started using ey-core instead of ey due to some issues with ey. We have multiple accounts with the same environment names (e.g. "production" and "staging") and existing implementation:
Was broken in terms of filtering by account.
Had an incorrect short flag for environments.
Made it impossible to get the servers for an environment that had the same name as an environment of the default account.
Additionally, the table output has been altered to include the public hostname. In our own use cases for ey this was probably the most regularly used information.
After transitioning our project to Ruby 2.4 we started using
ey-coreinstead ofeydue to some issues withey. We have multiple accounts with the same environment names (e.g. "production" and "staging") and existing implementation:Additionally, the table output has been altered to include the public hostname. In our own use cases for
eythis was probably the most regularly used information.