<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hello, <br>
<br>
You are right that the changes are only followed for
rules/directives/parameters/groups, and not techniques. <br>
The reason is a bad one (historically, "technique" was a bit appart,
with simpler update workflows, and we are working to set-them back
in the common one).<br>
<br>
The changes are still traced (you can see in "event logs" that a
technique changed, and of course the
`/var/rudder/configuration-repository` git repository store all
changes), but the UX is not yet the same as for rules/etc. We are
working on it. In 6.0, we did some backend changes that were
necessary to bring back together techniques and other configuration
elements, and in 7.0 (next year) they should have the same status as
other.<br>
<br>
The change validation plugin allows to add a validation workflow
(with mandatory review/validation) with the same scope. <br>
<br>
Hope it helps !<br>
<br>
<br>
<div class="moz-signature">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<table style="color:#666; font-size: 9pt; border-collapse:
collapse; font-weight: bold;" width="450" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr style="border-bottom: 1px solid #ddd;border-top: 1px solid
#ddd;">
<td colspan="2" style="text-align: center; padding: 5px;"> <a
href="http://www.rudder.io/"> <img
src="cid:part1.C26307D6.A803FE6D@rudder.io"> </a> </td>
<td colspan="2"> <b>François ARMAND</b><br>
<span style="font-weight:normal;">CTO<br>
<b>T:</b> +33 183 62 99 23 <b>M:</b> +33 663 37 60 55</span><br>
</td>
</tr>
</tbody>
</table>
</div>
<div class="moz-cite-prefix"><br>
<br>
On 14/11/2019 21:08, tim taler wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+=NtHw8i5e5Asi9Nmgd--cCm_76KABpPBZ4V_04sJd_yqYKDQ@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Hi all,
while evaluating rudder, momentarily with the (free) community version,
I see that "some" changes I do on the graphical frontend are leading
to a popup window that requests a comment on the policy change.
That is IMO a nice feature, making changes more transparent.
But than there are a whole bunch of changes I can do - even to active
techniques - which seems not to be tracked with a mandatory comment
(change of file attributes, add end remove of commands etc etc)
I don't quite understand why keeping track of "some" policy changes
but not of others; or do I miss something?
Does the licensed version behave the same?
Could I enforce the mandatory commenting (and thus keeping track) of
each and any change (at least of "active" policies, i.e. a policy that
is or could be applied to any potential instance in the pool)
TIA & best regards
_______________________________________________
rudder-users mailing list
FAQ: <a class="moz-txt-link-freetext" href="https://faq.rudder.io/">https://faq.rudder.io/</a>
Bug Tracker: <a class="moz-txt-link-freetext" href="https://issues.rudder.io/">https://issues.rudder.io/</a>
<a class="moz-txt-link-abbreviated" href="mailto:rudder-users@lists.rudder-project.org">rudder-users@lists.rudder-project.org</a>
<a class="moz-txt-link-freetext" href="https://www.rudder-project.org/mailman/listinfo/rudder-users">https://www.rudder-project.org/mailman/listinfo/rudder-users</a>
</pre>
</blockquote>
<br>
</body>
</html>