Business Context
A DevOps engineer is debugging a new deployment script. The script accidentally attempts to flag a backup as 'complete' without having initiated a transaction or a 'createBackup' step. This test verifies the system's robustness and error handling when the action is called out of context.
About the Set : accessControl
Management of access rights and data security.
Discover all actions of accessControl Data Preparation
Standard session start without assuming a transaction context.
Copied!
| 1 | |
| 2 | PROC CAS; |
| 3 | |
| 4 | ACCESSCONTROL.assumeRole / adminRole='superuser'; |
| 5 | |
| 6 | |
| 7 | RUN; |
| 8 |
Étapes de réalisation
1
Attempt to run completeBackup in isolation (out of transaction context).
Copied!
| 1 | PROC CAS; |
| 2 | ACCESSCONTROL.completeBackup; |
| 3 | RUN; |
Expected Result
The system should handle the isolated call gracefully. Depending on the exact internal implementation, it might log a warning that no backup is currently pending completion, or complete successfully as a no-op, but it must not crash the CAS session.