Bug #25532
open
An invalid technique yaml sometimes result in deletion of rudderc files
Description
After saving a technique with a typo in the yml from the yaml editor :
params: comman: echo "test"
, instead of
command: echo "test", an error notification is returned with the message MethodNotFound: Parameter 'command' for method 'command_execution' not found when writing dsc Technique 'Test tec' methods calls.The error message suggest that a
dsc Technique is attempted to be written even when the method is not compatible with the DSC agent e.g. with "command_execution_once".
But there is no "Complation output" tab in the technique interface, and the error only has a trace in the logs. In the directory of the technique in the filesystem, the metadata.xml and technique.ps1 are even removed from the filesystem, and I would have expected a compilation-output.yml file to be created with the details of the error but is also not there.
This is the case even with rudder.technique.compiler.app=rudderc configured to avoid webapp technique compilation fallback
Updated by Clark ANDRIANASOLO about 2 months ago
It seems to be related to error-handling. Taking the example of the following technique content :
method: command_execution_as_user params: command: test user: test
, when making a typo by typing
comman instead of command, there is no compilation-output.yml. But when making a typo with
use instead of user, there is a compilation-output.yml file.
It has been reproduced with the file_content method as well, with the path and lines parameters
Updated by Clark ANDRIANASOLO about 2 months ago
· Edited
When the compilation-output.yml is written, the "Compilation output" tab only appears after a refresh of the page, and not after clicking the "Save" button and after the error is displayed :
it is better but not yet satisfying : we need the compilation output tab to be displayed instantly
Updated by Vincent MEMBRÉ 15 days ago
- Target version changed from 8.1.8 to 8.1.9