how does pulumi handle rollback in kubernetes? specifically situations such as configmap linked to applications.. if previous upgrade was happened only to configmap, and not to application(kind: deployment).. during current upgrade if i encounter any issue, i can only rollback app (deployment), but can't get previous conifgmap.. Currently helm handles this with chart release history, wondering if pulumi can handle too