-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(maas_api): list agent connections #528
Conversation
This PR adds a new API call that recently landed in MaaS and Intelligence is starting to use. It's likely to become our new preferred way to test if an agent is connected, since the real API has superior performance when testing many agent connections at once.
Current coverage is
|
for dc in ('dfw1', 'ord1', 'lon3')] | ||
|
||
|
||
@attributes([Attribute('id', instance_of=text_type), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future, we should be moving to attrs
, rather than characteristic
. There's nothing wrong with Characteristic, and it is still maintained, but attrs has a few subtle advantages and eventually we'd like to be on just one utility library of this type. (You can really think of attrs as characteristic NG, it's a newer library by the same author for the same purpose.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm actually working on a PR upstream to redo this module in terms of attrs
, but wanted to get the feature out first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. Not a blocking comment.
Whoops. See immediately preceding referenced comment. |
feat(maas_api): list agent connections
Filed #531 . |
This PR adds a new API call that recently landed in MaaS and
Intelligence is starting to use. It's likely to become our new preferred
way to test if an agent is connected, since the real API has superior
performance when testing many agent connections at once.