scottyaslan commented on issue #3606: [WIP] Nifi 6282 URL: https://github.com/apache/nifi/pull/3606#issuecomment-525013059 > > Maybe we can just document that this is the case??? Otherwise the only solution I could come up with would be to update the parameter context with all the deletes first and then update the parameter context with the new or updated parameters... > > I don't think we could apply deletes then updates or updates then deletes. It depends on the order the user does them. > > Our options, as I see them, from easiest to hardest are: > > * Document this somewhere. > * Detect this scenario/failure and indicate to the user that if they may need/want to delete and add in separate operations. > * Change the backend API to support a more robust add/update/delete request that supports order... then update the front-end to deal with these changes. OK so it sounds to me like we just want to alert the user in a similar way to which we alert the user when they attempt to create a parameter with the same name as an existing parameter. We can just prompt the user to apply the deletion to the parameter context before attempting to recreate a parameter with the same name. Thoughts??? Does it matter if they are trying to recreate the parameter with the same sensitivity? At that point it is just an update to that parameter right???
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
