Skip to content

Conversation

@skaerg
Copy link
Contributor

@skaerg skaerg commented Nov 26, 2025

https://issues.rudder.io/issues/26653

This PR aims to clarify the purpose of the "reset status to be able to accept a different key" button :

  • The button is now labeled Reset certificate
  • There is a short explanation above the button that describes its purpose
  • The button and description only appear if the user clicks on the Show certificate button

<p>
You may wish to remove the certificate above in order to define a new one.
<br/>
In that case, you can <b>reset</b> this node's certificate : the certificate for this node will be undefined, and the next inventory will be trusted automatically.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
In that case, you can <b>reset</b> this node's certificate : the certificate for this node will be undefined, and the next inventory will be trusted automatically.
In that case, you can <b>reset</b> this node's certificate: the certificate for this node will be undefined, and the next inventory will be trusted automatically.

@skaerg
Copy link
Contributor Author

skaerg commented Nov 26, 2025

Commit modified

@skaerg skaerg force-pushed the enh_26653/improve_the_reset_status_to_be_able_to_accept_a_different_key_node_feature branch from 80e37e3 to 3abefa7 Compare November 26, 2025 16:40
<br/>
In that case, you can <b>reset</b> this node's certificate: the certificate for this node will be undefined, and the next inventory will be trusted automatically.
<br/>
You may define a different key for this node after the reset.
Copy link
Member

@amousset amousset Nov 26, 2025

Choose a reason for hiding this comment

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

Key or certificate? This lacks precision.

@skaerg
Copy link
Contributor Author

skaerg commented Dec 2, 2025

Commit modified

@skaerg skaerg force-pushed the enh_26653/improve_the_reset_status_to_be_able_to_accept_a_different_key_node_feature branch from 3abefa7 to ff2a2bf Compare December 2, 2025 10:07
@skaerg skaerg marked this pull request as ready for review December 2, 2025 10:13
@skaerg skaerg requested a review from amousset December 4, 2025 13:24
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

Successfully merging this pull request may close these issues.

2 participants