I’m currently using DevOps and Marketplace applications within Palantir to roll out changes that impact our ERP. My usual workflow is to develop everything on a dev environment first and then push it to production once I’m confident nothing will break. The problem I’m running into is that when I delete certain applications or folders in the dev environment, those deletions aren’t mirrored in production after deployment. Has anyone else faced this kind of issue or found a workaround? I’d appreciate any insights!
The Marketplace behavior is expected and aligns with DevOps best practices. In production environments, resources are generally not deleted; even in섭 cloud‑native applications, production deployments are typically non‑destructive. Deleting resources in PROD introduces the risk of irreversible data loss and weakens both auditability and rollback capabilities. It’s also important to keep in mind that a resource no longer used by a newer version of a product may still be depended on by other projects. From that perspective, this behavior is intentional and sensible, and proper coordination is required.
For this reason, I would recommend adjusting current practices. Instead of trashing or deleting unused resources, mark them as deprecated, or leverage project structure and place them in a dedicated Deprecated folder.
That said, when a product relies on Marketplace roles, I do have reservations about requiring an Owner to unlock the project in order to trash or delete resources. This creates “phantom” actions that are not reflected in the Marketplace product changelog, which makes auditability unclear and murky. We have submitted a feature request to Palantir to support a formal deprecation queue, with deprecation actions included as part of product packaging. However, this has not yet been prioritized.