-
Notifications
You must be signed in to change notification settings - Fork 73
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 #23039: Add rich form types to yaml techniques #4887
Fixes #23039: Add rich form types to yaml techniques #4887
Conversation
PR updated with a new commit |
6 similar comments
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
4 similar comments
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
6 similar comments
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
<CONSTRAINT> | ||
<TYPE>textarea</TYPE> | ||
<MAYBEEMPTY>true</MAYBEEMPTY> | ||
<TYPE>string</TYPE> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the change from textarea to string here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because previous code used to put textarea everywhere fro no reason
PR updated with a new commit |
This PR is not mergeable to upper versions. |
OK, squash merging this PR |
4b1d8f6
to
2fefd25
Compare
2fefd25
into
Normation:branches/rudder/8.0
https://issues.rudder.io/issues/23039
For the most part, adds support for all directive form niceties supported in the built-in techniques.
A few interesting points:
metadata.xml
. Particularly we use types as much as possible, and less constraints. Some values were renamed for either consistency with what is already there or just clarity.ParameterType
(scala)/Escaping
(rust) from technique parameters, this was a mistake we only have them on method parameters for now.