Project

General

Profile

Bug #4093

With Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message

Added by Nicolas PERRON over 4 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
5
Assignee:
-
Category:
Web - Config management
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Pull Request:
Priority:
0

Description

On Rudder 2.6 with Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message:
The form contains some errors,[...] could not save change request[...] java.util.NoSuchElementException: key not found: MY_NEW_ATTRIBUTE_WITHOUT_VALUE

To add value to the new attribute, I need to save the Directive with the new version of the Technique but this error message prevent me to do it.

History

#1 Updated by Nicolas PERRON over 4 years ago

  • Priority changed from 1 to 3
  • Target version changed from 2.6.9 to 2.6.10

#2 Updated by Nicolas CHARLES over 4 years ago

You should never never change attribute names without changing technique version. That's why you are having this issue

#3 Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.6.10 to 2.6.11

#4 Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.6.11 to 2.6.12

#5 Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.6.12 to 2.6.13

#6 Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.6.13 to 2.6.14

#7 Updated by Jonathan CLARKE about 4 years ago

  • Target version changed from 2.6.14 to 2.6.16

#8 Updated by Jonathan CLARKE about 4 years ago

  • Target version changed from 2.6.16 to 2.6.17

#9 Updated by Nicolas PERRON almost 4 years ago

  • Target version changed from 2.6.17 to 2.6.18

#10 Updated by Matthieu CERDA almost 4 years ago

  • Target version changed from 2.6.18 to 2.6.19

#11 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.6.19 to 2.6.20

#12 Updated by François ARMAND over 3 years ago

  • Subject changed from On Rudder 2.6 with Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message to With Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message
  • Status changed from New to Discussion
  • Priority changed from 3 to 5
  • Target version changed from 2.6.20 to 2.10.10

Not sur what to do about that, because it's a edge case (changing a Technique without changing its version but with workflows enables... )

Setting a low priority on it. The solution would be to have a full verisonning on Technique independant of the "human facing" version.

#13 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.10 to 2.10.11

#14 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.11 to 2.10.12

#15 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.12 to 2.10.13

#16 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.13 to 2.10.14

#17 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.10.14 to 2.10.15

#18 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.10.15 to 2.10.16

#19 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.10.16 to 2.10.17

#20 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.10.17 to 2.10.18

#21 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.10.18 to 2.10.19

#22 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.10.19 to 2.10.20

#23 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.10.20 to 2.11.18

#24 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.18 to 2.11.19

#25 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.19 to 2.11.20

#26 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.20 to 2.11.21

#27 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#28 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#29 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#30 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.24 to 308

#31 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 308 to 3.1.14

#32 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#33 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#34 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#35 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.17 to 3.1.18

#36 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.18 to 3.1.19

#37 Updated by François ARMAND over 1 year ago

  • Status changed from Discussion to Rejected
  • Priority set to 0

I'm closing that ticket because it is not a supported feature. We don't allow to change a mandatory technique attribute name without changing the technique version.

Also available in: Atom PDF