It seems like awless is unaware of geolocation, even when the column is explicitly included. querying for a record with geo entries yields a single record and it seems to be semi-random which one actually gets shown.
Actual
$ awless list records --filter name=snapshot.glympse.com --columns type,name,zone,alias,geolocation
| TYPE ▲ | NAME | ZONE | ALIAS | GEOLOCATION |
|--------|-----------------------|--------------|--------------------------------------------------------------------------------|-------------|
| A | snapshot.glympse.com. | glympse.com. | dualstack.p-s1-web-snapshot-service-1541530819.eu-central-1.elb.amazonaws.com. |
Expected (something like)
$ awless list records --filter name=snapshot.glympse.com --columns type,name,zone,alias,geolocation
| TYPE ▲ | NAME | ZONE | ALIAS | GEOLOCATION |
|--------|-----------------------|--------------|--------------------------------------------------------------------------------|-------------|
| A | snapshot.glympse.com. | glympse.com. | dualstack.p-s1-web-snapshot-service-1541530819.eu-central-1.elb.amazonaws.com. | EU |
| A | snapshot.glympse.com. | glympse.com. | dualstack.p-n0-web-snapshot-service-465391880.us-east-1.elb.amazonaws.com. | * |
Poked around the code and happy to contribute, but having some trouble finding the area of code to edit. Direction would be appreciated.
It seems like
awless
is unaware of geolocation, even when the column is explicitly included. querying for a record with geo entries yields a single record and it seems to be semi-random which one actually gets shown.Actual
Expected (something like)
Poked around the code and happy to contribute, but having some trouble finding the area of code to edit. Direction would be appreciated.