amalto platform6-client-nodejs issues

amalto / platform6-client-nodejs

:sparkles: Platform 6 Node.js client

MIT License

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

The method "getUserPermissions" works only with the dev b2auth

#18 roxanemace closed 6 years ago
0
Do not prefix the headers keys by 'platform6.'

#17 roxanemace closed 6 years ago
0
Update the URL of the Platform 6 documentation in the README.md

#16 roxanemace closed 6 years ago
0
Upgrade the version of the dependency Hazelcast node.js client

#15 roxanemace closed 6 years ago
0
Update CMB headers to match latest version of platform6

#14 simon-temple closed 6 years ago
2
The header "user" is no longer required by the service deployment

#13 simon-temple closed 6 years ago
0
CMB Response Checking

#12 simon-temple opened 6 years ago
1
Implement a continuous integration

#11 roxanemace closed 6 years ago
0
Create a documentation generated by JSDoc

#10 roxanemace opened 6 years ago
1
Get the Platform 6 instance's name through a common message

#9 roxanemace closed 6 years ago
0
Use `nyc` to check the code coverage

#8 roxanemace closed 6 years ago
1
A developer should be warned if a service with the same id is already deployed on the instance

#7 roxanemace closed 6 years ago
3
A developer should not be able to create a service with a non installed application key

#6 roxanemace opened 6 years ago
1
Implement a method to receive messages from Platform 6

#5 roxanemace closed 6 years ago
0
Implement unit tests for the different modules

#4 roxanemace opened 6 years ago
0
Add coverage badges on the README.md

#3 roxanemace closed 6 years ago
0
Update the structure of the CommonMessage object

#2 roxanemace closed 6 years ago
0
Expose methods to check that the user has the right permissions

#1 roxanemace closed 6 years ago
1