- 17 Feb, 2023 7 commits
-
-
Jérome Perrin authored
This is no longer guessed on Zope4
-
Jérome Perrin authored
this way we can just assert the full page content
-
Jérome Perrin authored
this does not depend on the details of the URL
-
Jérome Perrin authored
This change is from zope4
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
An error slipped in 92da569e (slapos_jio: Drop Handlebars, 2022-06-08)
-
- 13 Feb, 2023 1 commit
-
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!488
-
- 10 Feb, 2023 3 commits
-
-
Rafael Monnerat authored
Most liketly a copy and paste mistake
-
Rafael Monnerat authored
Whenever you define a slave, the option_index inst the software-type but the property of the dict/object.
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!487
-
- 09 Feb, 2023 1 commit
-
-
Rafael Monnerat authored
This category is used whenever the user wants disallow allocation for the time been. It do not intend to re-open again after a procedure or do not intend to terminate the machine, just dont want anything be allocated on it.
-
- 07 Feb, 2023 16 commits
-
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!486
-
Rafael Monnerat authored
category close and not closed, and do not auto cancel upgrades for computers for termination. This should be handled by setting never on upgrade scope.
-
Rafael Monnerat authored
Those actions were dropped from ancient site and forgotten to be removed.
-
Rafael Monnerat authored
Only Monitor Scope should be taken into account.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Whenever allocation scope changes, the capacity is close, and the proper alarm will re-open it later a moment after. This prevents when you change from close to open, to get a miss-updated window, and something is allocated before it capacity is calculated. Do not touch on monitor scope, except when it is None or allocation is "Close Forever", this allow the user to keep monitoring closed computers (Maintenance, termination...), since ONLY allocation is closed, and the computer is supposed to work normally with whatever is inside.
-
Rafael Monnerat authored
-
Romain Courteaud authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
... to decide which computers to select for check for upgrades
-
Rafael Monnerat authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
- 06 Feb, 2023 1 commit
-
-
Łukasz Nowak authored
It's very useful in some deployments to control maximum time of partition processing. This parmater can end up in slapos.cfg configuration file or command line.
-
- 03 Feb, 2023 1 commit
-
-
Thomas Gambier authored
-
- 01 Feb, 2023 4 commits
-
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!480
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!485
-
Łukasz Nowak authored
-
Rafael Monnerat authored
-
- 31 Jan, 2023 6 commits
-
-
Rafael Monnerat authored
... to make publication_url happy
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Since the accounting workflow introduced Guard on start transition, it is required assignee or assignor to change the state (before Modify Portal content was enough). The script is invoke as Shadow user, and since destination section is set, the User automatically become Auditor (rather them Assignee) so it would imply a deeper change to relax security for the shadow user (not shadow person) just to invoke start. Not to mention HUGE security update to be done. Use Manager proxy role is not ideal, but it doesn't introduce a security issue while solve the problem until a deeper review on the roles for Shadow users takes place.
-
Rafael Monnerat authored
Export last workflow state for Business Processes
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!481
-
Rafael Monnerat authored
Since instances typically only access master once a day, double the cache duration to ensure it wasnt flushed between the runs.
-