Added comment on possible error and wording in the expect message.

Author: soenkeliebau

rust/krb5-provision-keytab/src/lib.rs

@@ -34,6 +34,7 @@ pub enum AdminBackend {
         generate_sam_account_name: Option<ActiveDirectorySamAccountNameRules>,
     },
 }
+
 #[derive(Serialize, Deserialize, Debug)]
 pub struct ActiveDirectorySamAccountNameRules {
     pub prefix: String,
@@ -96,7 +97,10 @@ pub async fn provision_keytab(krb5_config_path: &Path, req: &Request) -> Result<
     let mut stdin = child
         .stdin
         .take()
-        .expect("Failed to read from stdin of stackable-krb5-provision-keytab command! ");
+        // a failure here has some fundamental reason like us taking ownership of the pipe
+        // earlier, which is most probably more a coding than a runtime error - this is
+        // why this error is not handled here, but we panic instead
+        .expect("Failed to take ownership of stdin pipe of stackable-krb5-provision-keytab command! ");
     stdin.write_all(&req_str).await.context(WriteRequestSnafu)?;
     stdin.flush().await.context(WriteRequestSnafu)?;
     drop(stdin);