You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already discussed 'in real life' there are some variables with misleading names.
The variable ca_host inside the API feature for example is incorrect from an Icinga 2 technical point of view, as the "parent host" must be specified here in a distributed system with satellites. Naming to parent_host or similar would be more suitable.
Other examples are ca_host_port and icinga2_delegate_to.
As @mkayontour said, we need to make sure to have a transition phase for that. We could deprecate them and remove them in future versions.
The text was updated successfully, but these errors were encountered:
The way this feature works, ca_host is the correct name to go with, in my opinion, as the collection will indeed default to delegating the certificate creation to the ca_host.
As already discussed 'in real life' there are some variables with misleading names.
The variable
ca_host
inside the API feature for example is incorrect from an Icinga 2 technical point of view, as the "parent host" must be specified here in a distributed system with satellites. Naming toparent_host
or similar would be more suitable.Other examples are
ca_host_port
andicinga2_delegate_to
.As @mkayontour said, we need to make sure to have a transition phase for that. We could deprecate them and remove them in future versions.
The text was updated successfully, but these errors were encountered: