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

Rename conflict check #1194

Open
t-woerner opened this issue Dec 20, 2023 · 0 comments
Open

Rename conflict check #1194

t-woerner opened this issue Dec 20, 2023 · 0 comments

Comments

@t-woerner
Copy link
Member

t-woerner commented Dec 20, 2023

There should be a conflict check for state: renamed, especially for modules that support to apply multi item changes like for example ipauser and ipagroup.

The check should ensure that a multi item change with a name conflict is failing as a complete transaction before a single change is applied. For each rename, there needs to be a check that there is no existing item with the same name and also that there is no name conflict (name and rename) within the transaction. Additional complexity due to sorting of the items to fix name conflicts within the transaction is not the goal.

Related: #1174 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant