Bug #25545: Techniques no longer compile with error in rudderc arguments - Rudder - Issue Tracker

Actions

Copy link

Bug #25545

open

Techniques no longer compile with error in rudderc arguments

Added by Clark ANDRIANASOLO 1 day ago. Updated about 1 hour ago.

Status:

Pending release

Priority:

N/A

Assignee:

François ARMAND

Category:

Techniques

Target version:

8.2.0~beta2

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Critical - prevents main use of Rudder | no workaround | data loss | security

UX impact:

I dislike using that feature

User visibility:

Getting started - demo | first install | Technique editor and level 1 Techniques

Effort required:

Very Small

Priority:

146

Name check:

To do

Fix check:

To do

Regression:

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

Related issues 1 (1 open — 0 closed)