- 20 Sep, 2017 4 commits
-
-
Rafael Monnerat authored
The skins should be automatically indexed while install the bt5s.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
The new implementation with hateoas API is under development so there is no need to expent time on fix those tests now.
-
Rafael Monnerat authored
-
- 19 Sep, 2017 1 commit
-
-
Alain Takoudjou authored
This pluging can be used a add a script which wipe data before the partition is removed The script run after all partition services are stopped. The script is ran by supervisord then slapos node report will wait until it finish before destroy the partition. /reviewed-on nexedi/slapos.core!23
-
- 14 Sep, 2017 1 commit
-
-
Alain Takoudjou authored
This pluging can be used a add a script which wipe data before the partition is removed The script run after all partition services are stopped. The script is ran by supervisord then slapos node report will wait until it finish before destroy the partition. /reviewed-on nexedi/slapos.core!22
-
- 14 Aug, 2017 5 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
No need 2 bt5 with similar goal.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
This code is old code for JIO which were never used in the end, clean up for the next implementation.
-
Rafael Monnerat authored
-
- 11 Aug, 2017 1 commit
-
-
Rafael Monnerat authored
This change were commited by mistake
-
- 02 Aug, 2017 6 commits
-
-
Rafael Monnerat authored
Get the person created by searching the ERP5 Login, because person has not reference defined.
-
Rafael Monnerat authored
- Use getUserId instead getReference for person login on self.login method - Get the person created by searching the ERP5 Login, because person has not reference defined.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
slapos_erp5: testSlapOSERP5LocalPermissionSlapOSInteractionWorkflow use person.getUserId instead person.getReference
-
- 01 Aug, 2017 4 commits
-
-
Rafael Monnerat authored
Follow up changes on erp5 security.
-
Rafael Monnerat authored
Follow up implementation of ERP5LoginUserManager.
-
Rafael Monnerat authored
Follow up changes from ERP5Security.
-
Rafael Monnerat authored
This API was changed, so follow up changes which come from ERP5.
-
- 31 Jul, 2017 2 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Remove useless imports Use ERP5Security.SUPER_SUPER instead SUPER_USER to follow up original code. Also use UnrestrictedMethod on SlapOSShadowAuthenticationPlugin
-
- 29 Jul, 2017 1 commit
-
-
Rafael Monnerat authored
Reference commit erp5@455b24e5
-
- 28 Jul, 2017 1 commit
-
-
Rafael Monnerat authored
This change follow changes on ERP5 code base: erp5@4b16e1dd
-
- 27 Jul, 2017 1 commit
-
-
Rafael Monnerat authored
-
- 24 Jul, 2017 1 commit
-
-
Rafael Monnerat authored
By invoking validate, the interaction workflow will be kicked and allocation will be triggered. In order to control the invocation order on the test, use portal_workflow API.
-
- 11 Jul, 2017 4 commits
-
-
Rafael Monnerat authored
This test is failing as it is incompatible with the latest version of renderjs. The Monitor UI is going to be merged into RenderJS, so keep this test as an expected failure until this test be moved along with monitor implementation to ERP5/OfficeJS repository.
-
Rafael Monnerat authored
Person.getTitle do not contains patches for a while so we fall back on default the implementation of ERP5. This don't require mantains a test on project scope.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
- 10 Jul, 2017 1 commit
-
-
Rafael Monnerat authored
-
- 04 Jul, 2017 2 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
This will prevent mistaken information when display the used amount of instances.
-
- 03 Jul, 2017 1 commit
-
-
Tomáš Peterka authored
Move manager.instance to the part of code which doesn't get preempted /reviewed-on nexedi/slapos.core!21
-
- 30 Jun, 2017 4 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
The logic implemented on client is (for started instances): Notify instances are available to master run promises if fail report error Notify instances are started to master The change on this commit prevent us to consider the notification of availability as "no error", as promise can still fail, so we just ignore and let the decision to suspend for the next run.
-
Rafael Monnerat authored
This makes the ease to get the message, on certain special cases.
-