Project

General

Profile

Actions

Bug #16850

closed

package_state_options doesn't properly defines outcome classes when called twice with same package name

Added by Nicolas CHARLES almost 5 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Category:
Generic methods
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

i we want to enforce that a package is there, and upgrade it on a second call, package_state_options won't define properly classes has ncf_package_${canonified_state}_${canonified_name} is not precise enough


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #16849: When using twice directive packageManagement 1.2, once to ensure presence of a package, and second one to upgrade the package, reporting and posthook is wrong on the second oneReleasedBenoît PECCATTEActions
Actions

Also available in: Atom PDF