search

dlr-eoc / prosEO

prosEO – A Processing System for Earth Observation Data
GNU General Public License v3.0
14 stars 1 forks source link

Production Planner does not increment order version numbers #46

Closed tangobravo62 closed 4 years ago

tangobravo62 commented 4 years ago

When updating a ProcessingOrder, the Production Planner does not increment the object version number:

prosEO> order show L2_orbits_3000-3002
---
- id: 87
  version: 1
  missionCode: "PTM"
  identifier: "L2_orbits_3000-3002"
  [...]

prosEO> order approve L2_orbits_3000-3002
(I2942) Order with identifier L2_orbits_3000-3002 approved (new version 2)

prosEO> order plan L2_orbits_3000-3002 telekom-otc
(I2943) Order with identifier L2_orbits_3000-3002 planned (new version 2)

The "new version" should have been 3 after approve and 4 after plan.

emelchinger commented 4 years ago

Implemented, each state change of order, job and job step increments version number: Example for order:

prosEO> order approve L2orbits3000-3002-1
(I2942) Order with identifier L2orbits3000-3002-1 approved (new version 2)
prosEO> order plan L2orbits3000-3002-1 Lerchenhof
(I2943) Order with identifier L2orbits3000-3002-1 planned (new version 3)
prosEO> order release L2orbits3000-3002-1
(I2944) Order with identifier L2orbits3000-3002-1 released (new version 5) <-- intended, 
In this case the state changes are PLANNED -> RELEASED -> RUNNING