Update Userdata need Provision again

[matthewei]

User Story
Sometimes the user want to update userdata or networkdata. But now we create a new secret and update the BMH's spec. The bmo can't provision it again.

Detailed Description

1. create a new usetdate secret or networkdate secret
2. update the userdate secret
3. the bmh provision again

/kind feature

[metal3-io-bot]

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dtantsur]

A more general feature (and also easier and less risky to add) would be some sort of a "rebuild annotation" (similar to the existing reboot annotation) then tells BMO to rebuild the instance, no matter what changed (or even if nothing changed).

[Rozzii]

We have discussed this in the 2024.12.04 Community meeting and the consensus was that we would not accept this proposal in the current form.

Our issues with this are:

• Very minor convinience feature that requires considerable work yet wouldn't really improve functionality
• The current proposal is prone to accidental reprovisioning

We have concluded that the more general feature mentioned by @dtantsur would be a better approach.

[Rozzii]

/triage unresolved