Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #19059: rework 6.2.3/6.2.4 release notes #657

Merged

Conversation

amousset
Copy link
Member

To prevent this type of problems (in the scope of a patch release) we had to totally prevent passing empty parameters to techniques from the technique editor. This makes missing parameters a policy generation error, allowing to safely provide
them to directives after modifying the source technique.

This may break existing directives that rely on an empty parameter (wether with an empty value or with an expression evaluating to an empty value, like a property containing an empty string).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you could not set an empty value on this field

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was rejected, only the case where you use a property with a default value is broken

@amousset
Copy link
Member Author

PR updated with a new commit

To prevent this type of problems (in the scope of a patch release) we had to totally prevent passing empty parameters to techniques from the technique editor. This makes missing parameters a policy generation error, allowing to safely provide
them to directives after modifying the source technique.

This may break existing directives that rely on an expression evaluating to an empty value, like a property containing an empty string, or a property value with an empty default.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

evaluating -> Which evaluates

@amousset
Copy link
Member Author

PR updated with a new commit

@Normation-Quality-Assistant

This PR is not mergeable to upper versions.
Since it is "Ready for merge" you must merge it by yourself using the following command:
rudder-dev merge https://github.com/Normation/rudder-tools/pull/657
-- Your faithful QA
Kant merge: "Science is organized knowledge. Wisdom is organized life."
(https://ci.normation.com/jenkins/job/merge-accepted-pr/36788/console)

@amousset
Copy link
Member Author

OK, squash merging this PR

@amousset amousset force-pushed the bug_19059/rework_6_2_3_6_2_4_release_notes branch from 9354bc6 to f5234e2 Compare March 23, 2021 13:45
@amousset amousset merged commit f5234e2 into Normation:master Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants