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 #13810: Update ldap node entries from ipNetworkNumber => networkSubnet #2061

Conversation

fanf
Copy link
Member

@fanf fanf commented Nov 12, 2018

@@ -175,6 +175,7 @@ ldap.attr.networkInterfaceType = Interface type
ldap.attr.networkInterfaceTypeMib = Interface type (Mib)
ldap.attr.ipHostNumber = IP address
ldap.attr.ipNetworkNumber = Network
ldap.attr.networkSubnet = Network
Copy link
Member

Choose a reason for hiding this comment

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

Should it not be different ? like "Subnet" instead of "Network"

@fanf
Copy link
Member Author

fanf commented Nov 12, 2018

Actually, this should be done in a migration script. There is no reason to do it at each start of rudder. Moreover, with a migration script, we are sure that dyn-groups are not impacted, since rudder is always shutdown during the whole migration process.

@fanf fanf closed this Nov 12, 2018
@fanf fanf deleted the bug_13810/update_ldap_node_entries_from_ipnetworknumber_networksubnet branch March 15, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants