You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now it is possible to define to deployment_flavours keys in the NSD. This doesn't trigger any error in the schema validation and the parsing library only gives the last value.
This could lead to problems if the developer doesn't realize that some key is duplicated and it's only looking at the values of the first one. In order to prevent this from happening we are going to explore options to check the duplicates by reading the descriptor file directly as text or (preferably) using other existing library.
The text was updated successfully, but these errors were encountered:
Right now it is possible to define to deployment_flavours keys in the NSD. This doesn't trigger any error in the schema validation and the parsing library only gives the last value.
This could lead to problems if the developer doesn't realize that some key is duplicated and it's only looking at the values of the first one. In order to prevent this from happening we are going to explore options to check the duplicates by reading the descriptor file directly as text or (preferably) using other existing library.
The text was updated successfully, but these errors were encountered: