feat: refresh variables when switching service

[PaulFarault]

Fixes #169

Which issue(s) this PR fixes

Fixes #169

Additional comments

Agreements

• [X] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
• [X] I hereby agree to grant TOSIT a copyright license to use my contributions.

[mdrutel]

Use Case :

• Click on the "spark" service
• Modify the spark_version attribute
• Click on "Validate" button
• Click on another service, eg. hadoop
• Click on the "spark" service

Result : the attribute is not modified

[mdrutel]

addendum : when i refresh another time, the modification is OK ^^'

[PaulFarault]

You're right, the value is well actualized in the store but not showed. I'll investigate 👀

[PaulFarault]

TL;DR @mdrutel this should work as expected now

The problem was that we are using uncontrolled form. When loading the page, the field is initialized using the defaultValue which is not updated along with the state, even if the store is refreshed.

Ideally, we could use controlled form to update the field. This could be worked along with #164.

My solution was to initialize the defaultValue with right value since the beginning. I did it by re-fetch the value from the server directly after a successful PUT operation.

[pvalentin01]

Use case 1 :

• Click on Services "spark3"
• Modify spark_version attribute
• Click on "Validate" button
• Click on "View" button

Result : The attribute is modified

Use case 2 :

• Click on Services "spark3"
• Modify spark_version attribute
• Click on "Validate" button
• Click on another service
• Click on Services "spark3"

Result : The attribute is modified

[mdrutel]

Now it's all fine, variable values are well refreshed ^^