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

Pulumi doesn’t have a separate rollback command. Instead, you can revert to a previous version of your Pulumi program and then run an update (i.e., roll forward to roll back). I’m not sure if that answers your question?

@gorgeous-egg-16927 thats correct, we are currently relaying on git commits/versioning.. i wanted to check if pulumi support rollback feature. Thanks