Bug #25545
closedTechniques no longer compile with error in rudderc arguments
Description
I can no longer create a technique or change a technique that has no compilation-config.yml
with some args
: it causes an error on the technique editor every time I attempt to save (and even no "Compilation output" tab).
Since #25504 a new args
fields have been added for support in the compilation-config.yml
file for a technique, to build with additional command line arguments.
But when there is no such file the default argument is the empty string, which causes this compilation-output.yml
file to be written :
compiler: rudderc resultCode: 2 fileStatus: [] msg: 'Exit code=2 for technique: ''/var/rudder/configuration-repository/techniques/ncf_techniques/mytechnique/1.0''.' stdout: '' stderr: | error: unrecognized subcommand '' Usage: rudderc [OPTIONS] <COMMAND> For more information, try '--help'.
The trace logs for the command that is executed does not suggest that an empty argument is passed as first argument or Rudderc :
DEBUG techniques.writer.rudderc - Run rudderc: /opt/rudder/bin/rudderc --directory /var/rudder/configuration-repository/techniques/ncf_techniques/mytechnique/1.0 build
Updated by Clark ANDRIANASOLO 3 months ago
- Related to Architecture #25504: Remove webapp technique compilation fallback added
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5899
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|6619a2b1350458f03ae2494c3e095be7708b7f6e.
Updated by Vincent MEMBRÉ 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~rc1 which was released today.