Skip to content
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

Implement function to make users to admins #12

Open
noqqe opened this issue Jan 7, 2019 · 8 comments
Open

Implement function to make users to admins #12

noqqe opened this issue Jan 7, 2019 · 8 comments
Labels
enhancement New feature or request

Comments

@noqqe
Copy link
Member

noqqe commented Jan 7, 2019

No description provided.

@noqqe noqqe added the enhancement New feature or request label Jan 7, 2019
@noqqe
Copy link
Member Author

noqqe commented Jan 8, 2019

waiting for k4cg/matomat-service#11

@noqqe noqqe added the blocked Currently not solvalble in frontend label Jan 9, 2019
@blarz
Copy link
Contributor

blarz commented Aug 1, 2019

Not blocked anymore as far as I can see

@blarz
Copy link
Contributor

blarz commented Aug 8, 2019

The problem is: I don't how to "sync" the API or update the auto generated swagger files.
Can we add some documentation for this?

@noqqe
Copy link
Member Author

noqqe commented Aug 12, 2019

@blarz the command to update the swagger_client is

swagger-codegen generate -i https://raw.githubusercontent.com/k4cg/matomat-service/master/maas.yml -l python -o .

I dont know where to document this, as README.md is getting overwritten everytime we do the update. New File?

@blarz
Copy link
Contributor

blarz commented Aug 12, 2019

Brr I think I got it running, thanks. Will open a PR after cleaning the diff

@blarz blarz removed the blocked Currently not solvalble in frontend label Aug 17, 2019
@winterMate
Copy link
Contributor

@blarz I just fixed a typo in the MaaS API definition file 'maas.yml' in the MaaS project. Perhaps the issue is related to it. (Any client generated with the broken maas.yml will probably be dysfunctional)

@blarz
Copy link
Contributor

blarz commented Aug 23, 2019

@dagonc Awesome, thank you! I will re-generate and try it out over the weekend :)

@blarz
Copy link
Contributor

blarz commented Aug 26, 2019

@blarz I just fixed a typo in the MaaS API definition file 'maas.yml' in the MaaS project. Perhaps the issue is related to it. (Any client generated with the broken maas.yml will probably be dysfunctional)

@dagonc So I tried it and regenerated the API with the latest version of maas.yml, but it is still broken.

The problem I'm seeing is that auth_login_post returns a list of AuthSuccess elemets.
Printing all of them gives me three "empty" AuthSuccess elements, like this

[{'expires': None, 'token': None, 'user': None},
 {'expires': None, 'token': None, 'user': None},
 {'expires': None, 'token': None, 'user': None}]

Used like this:

        auth = auth_client.auth_login_post(user, password, validityseconds=42)
        pprint.pprint(auth)
        exit(1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants