Add v0 0 43 (#47)

* initial insert of v43

* TODO: fix model changes

* first unit test fixed

* updated to SLURM REST API v0.0.43

* bump some vulnerable dependency versions

* update docker container SLURM version to 25

* resolve changed endpoint name (to slurm_v0043_post_job)

FIXED UNIT AND INTEGRATION TESTS

* add partition info class

* see if integration test works with slurm 24 instead of 25

* try new v25 image

* check user filter before job resources

* fixes to docker setup and integration tests

* back original port value for docker slurm instance

Author: carstenschelp-surf

.github/workflows/unit_tests.yml

@@ -33,7 +33,7 @@ jobs:
       - name: Start Slurm Container and run pytest
         run: |
           echo "Starting slurm test container"
-          nohup docker run -p 10022:22  -p 6821:6820 --name testslurm --privileged  ghcr.io/xenon-middleware/slurm:23 -d &
+          nohup docker run -p 10022:22  -p 6821:6820 --name testslurm --privileged  ghcr.io/xenon-middleware/slurm:25 -d &
           pid=$!
           
           # Wait for container to become healthy

README.md

@@ -24,7 +24,7 @@
 
 SLURM CLI-API Proxy client is a tool designed to bridge existing applications and scripts that rely on the SLURM CLI. The tool mimics a selection of SLURM CLI commands, translating them into REST API calls, enabling seamless integration of existing tools with external SLURM workload managers. 
 
-Due to the extensive range of optional SLURM command arguments, only a limited subset is supported. However, the tool is designed for flexibility—the support to new arguments can be easily enabled by mapping them to the corresponding API request parameters or payload properties. Additionally, the design prioritizes extensibility, allowing support for alternative SLURM API versions (currently working with v0.0.39). The [developers documentation](https://slurm-cli-api-proxy.github.io/SLURM-CLI-API-Proxy-client/) provides further details on these design elements.
+Due to the extensive range of optional SLURM command arguments, only a limited subset is supported. However, the tool is designed for flexibility—the support to new arguments can be easily enabled by mapping them to the corresponding API request parameters or payload properties. Additionally, the design prioritizes extensibility, allowing support for alternative SLURM API versions (currently working with v0.0.39 or v0.0.43). The [developers documentation](https://slurm-cli-api-proxy.github.io/SLURM-CLI-API-Proxy-client/) provides further details on these design elements.
 
 
 

docs/limitations.md

@@ -1,7 +1,7 @@
 # Limitations & mismatches between the local CLI and the Proxy CLI
 
 
-## sbatch (v0.0.39)
+## sbatch (v0.0.39, v0.0.43)
 
 
 - The real `sbatch` command validates the input script for inconsistencies (e.g., the first line not starting with start with #!) and prevent the job to be started. When using the sbatch proxy, the content of the script is submitted as part of the corresponding API request. Therefore, when inconsistent slurm scripts are used with the proxy, a new job will be started, and eventually fail once the slurmctld process it.
@@ -12,7 +12,7 @@
     sbatch --job-name dajob --chdir /home/hcadavid  tests/slurm_test_scripts/slurm_write_job.sh
     ```
 
-## scontrol  (v0.0.39)
+## scontrol  (v0.0.39, v0.0.43)
 
 - Only job updates are supported. Node, partition and reservation resources are immutable in the SLURM API (only GET method).
 - Only one job can be updated at a time: only the '/job/{job_id}' endpoint (for a single job) is available.