Releases: thatmattlove/hyperglass
v1.0.0-beta.82
BREAKING CHANGE
NodeJS 14.15 or later is required. See the docs for installation instructions.
Fixed
- #135: Fix an issue where Juniper indirect next-hops were empty.
- Fix an issue where Juniper structured AS_PATH or Community queries would appear to fail if one address family (IPv4 or IPv6) had an empty response. For example, if an AS_PATH query for
.* 29414 .*
was made (which only returns IPv4 routes), the query would fail.
Changed
- Updated major Python dependencies (FastAPI, Scrapli, Netmiko, Pydantic, Uvicorn, Gunicorn, etc.)
- Updated UI dependencies
- #128: Add
best
to all Juniper BGP Route queries. See Juniper docs for more details.
Added
- The driver for devices can now be overridden with the
driver
parameter.
v1.0.0-beta.81
Fixed
- #124: Fix an issue where networks weren't always sorted alphabetically.
- #126: Fix rendering of markdown tables.
- #132: Fix an issue where iBGP routes on Arista devices caused output parsing to fail.
- #133: Use body styles for background/foreground color, allowing the user to override the
light
anddark
colors per the docs. - Fix an issue with select menu list style.
v1.0.0-beta.80
Fixed
- Fix an issue where the UI did not properly filter and detect the correct Query VRF when only one was defined.
- #121 Fix issue with select menu styling in light mode.
v1.0.0-beta.79
BREAKING CHANGE
Major changes have been made to how VRFs are defined and handled. Previously, you would signal to hyperglass that a VRF was the "default" VRF (meaning, a VRF does not need to be specified in any commands) by setting name: default
in the VRF block. This limitation meant that a VRF named default
had to be defined, and that any users who keep their global routing table in a non-default VRF must define it separately.
Moving forward, the name
field is only used to define the name of the VRF as known by the device. To signal that hyperglass should use the device's default VRF, set default: true
on the VRF. This is not the default.
Fixed
- Fix an issue where long-running commands, such as traceroutes that never complete, time out and display an error instead of the output.
Changed
- Don't do external RPKI lookups for non global unicast prefixes.
- Migrate to palette-by-numbers for theming.
- Update UI dependencies.
v1.0.0-beta.78
Added
- Experimental table output/structured data support for Arista EOS.
Fixed
- Corrected warning color on active routes in table output.
Changed
- Caught fetch errors now display the HTTP status text in the UI, instead of the caught error message.
v1.0.0-beta.77
POTENTIALLY BREAKING CHANGE: The device display_name
field is being deprecated, in favor of a single name
field, which will be displayed to the end user. The display_name
field still works, but you should migrate away from it as soon as possible.
Fixed
- #117: Fix naming and mapping of the Arista EOS driver.
arista
andarista_eos
will both work now.
Changed
- Removed
display_name
field from device model. Thename
field will be used in the UI. If adisplay_name
is defined, it will be used, for backwards compatibility.
v1.0.0-beta.76
NOTICE: hyperglass-agent will be deprecated soon. Use frr_ssh
or bird_ssh
for SSH connectivity in the meantime.
Added
- FRR & BIRD may now be accessed via standard SSH using the
frr_ssh
andbird_ssh
NOS. See the docs for important caveats.
Changed
port
indevices.yaml
now defaults to 22 if not specified.
Fixed
- AS Path graph view now uses dagre to properly arrange each AS.
- Added timeout argument to
hyperglass start --build
- fixes issue where running a UI build in this way failed due to a missing timeout argument error.
v1.0.0-beta.75
Changed
- Default UI build timeout is now 180 seconds.
- The hyperglass
build-ui
CLI command now accepts a--timeout
argument to override the UI build timeout.
v1.0.0-beta.74
Changed
- The Scrapli driver no longer specifically ignores the system's SSH config file.
- Updated UI dependencies.
Fixed
- #109: Remove the custom error page, because it doesn't work and doesn't really add much.