Rename change_key() to update_key()

Author: djc

src/account.rs

@@ -332,15 +332,15 @@ impl Account {
         &self.inner.id
     }
 
-    /// Account key rollover
+    /// Update the account's authentication key
     ///
     /// This is useful if you want to change the ACME account key of an existing account, e.g.
     /// to mitigate the risk of a key compromise. This method creates a new client key and changes
     /// the key associated with the existing account. `self` will be updated with the new key,
     /// and a fresh set of [`AccountCredentials`] will be returned to update stored credentials.
     ///
     /// See <https://datatracker.ietf.org/doc/html/rfc8555#section-7.3.5> for more information.
-    pub async fn change_key(&mut self) -> Result<AccountCredentials, Error> {
+    pub async fn update_key(&mut self) -> Result<AccountCredentials, Error> {
         let new_key_url = match self.inner.client.directory.key_change.as_deref() {
             Some(url) => url,
             None => return Err("Account key rollover not supported by ACME CA".into()),

tests/pebble.rs

@@ -334,15 +334,15 @@ async fn update_contacts() -> Result<(), Box<dyn StdError>> {
 
 #[tokio::test]
 #[ignore]
-async fn change_key() -> Result<(), Box<dyn StdError>> {
+async fn update_key() -> Result<(), Box<dyn StdError>> {
     try_tracing_init();
 
     // Creat an env/initial account
     let mut env = Environment::new(EnvironmentConfig::default()).await?;
     let old_account = env.account.clone();
 
     // Change the account key
-    let new_credentials = env.account.change_key().await?;
+    let new_credentials = env.account.update_key().await?;
 
     // Using the old ACME account key should now produce malformed error.
     let Err(Error::Api(problem)) = old_account