feat: add loggedin user account related entities and API endpoint interactions

[sachin120]

What does this implement

Added user account-related API

• Create Authorisation Token
• Delete Authorisation Token
• List Authorisation Tokens
• Update Token Name

[troyanov]

Hi @sachin120
Thank you for your contribution 👍

LGTM and +1
May I ask you to resolve the conflict at client/client.go? If you don't have time, we can take care of that.

[skatsaounis]

Hi @sachin120,

It seems that you need to create two entities since MAAS returns different response on listing tokens and at create response. Please take a look at the example:

ubuntu@maas-dev:~$ maas admin account create-authorisation-token
Success.
Machine-readable output follows:
{"token_key": "abcabc", "token_secret": "123123", "consumer_key": "!@#!@#", "name": "MAAS consumer"}

ubuntu@maas-dev:~$ maas admin account list-authorisation-tokens
Success.
Machine-readable output follows:
[
    {
        "name": "MAAS consumer",
        "token": "!@#!@#:abcabc:123123"
    }
]

So we need an entity for each one of them. Please update your PR and I will be glad to merge it 🙂

[sachin120]

Hi @sachin120,

It seems that you need to create two entities since MAAS returns different response on listing tokens and at create response. Please take a look at the example:

ubuntu@maas-dev:~$ maas admin account create-authorisation-token
Success.
Machine-readable output follows:
{"token_key": "abcabc", "token_secret": "123123", "consumer_key": "!@#!@#", "name": "MAAS consumer"}

ubuntu@maas-dev:~$ maas admin account list-authorisation-tokens
Success.
Machine-readable output follows:
[
    {
        "name": "MAAS consumer",
        "token": "!@#!@#:abcabc:123123"
    }
]

So we need an entity for each one of them. Please update your PR and I will be glad to merge it 🙂

I missed it. Thanks @skatsaounis

[troyanov]

Just a nitpick, I think AuthorisationTokenListItem will be a less confusing name for a variable.

[skatsaounis]

LGTM +1 Thanks for yet another contribution 🎉