Can I package resources from a Foundry Branch in a marketplace product via Devops?

Ask the Community
,
1

I want to have a way to publish “hotfixes” to my production projects.

Let’s assume I have 2 projects:

  • Dev project
  • Prod project

In a git-like environment, I would keep the main branch in the dev project to what is currently in production, while I work on feature on a branch.
Once the features/next “release” is ready, then I would merge it to master to be picked up for the next release on production project.

image
image1067×569 46 KB

If an issue in production arises by then, I can directly fix the main branch in the dev project, repackage and deploy in production.

image
image1127×617 55.2 KB

This works today in Foundry. I can develop in the “dev project” on a branch, once ready, merge to the main branch, package and push to production.

Now let’s assume I have 3 projects:

  • Dev project
  • Test project
  • Prod project

Idea 1
In that case, I need to:

  1. Keep on the main branch of the dev project the version pushed to production
  2. Work on new feature on another branch in the dev project
  3. Package the branch in a marketplace product and install it in the “test project” for testing
  4. If this works well, merge the change from the feature branch of the dev project to the main branch
  5. Package from this main and install in both Test and Prod

image
image1222×626 46.5 KB

If a hotfix needs to be applied, I can (most of the time) directly change the main branch of dev, repackage and redeploy to production.

image
image1083×681 70.4 KB

Problem: Marketplace doesn’t seem to support today packaging from branches.

Idea 2
In that case, I need to:

  1. Work on new feature on a branch in the dev project
  2. Once happy with the changes, merge to the main branch of the dev project
  3. Package the main branch and install it to Test project
  4. Once happy with the changes, re-package from Test project and install to production.

image
image1351×484 53.9 KB

If a hotfix needs to be applied, I can (at all time) directly redeploy the production version in the “Test project”, do the change, repackage from Test project and install with the hotfix in production.

  1. Package the branch in a marketplace product and install it in the “test project” for testing
  2. If this works well, merge the change from the feature branch of the dev project to the main branch
  3. Package from this main and install in both Test and Prod

image
image1145×631 65.7 KB

Two issues there: 1/ I need to repackage from Test, which can be error prone and add friction 2/ I need to keep track of the mapping of versions between the first and the second marketplace product, so that I can reinstall the “latest production-equivalent product” in Test project

Are there better approaches available today to support those workflows ?

2

Hi @VincentF

The topic you’re raising is both interesting and important, particularly in scenarios where Foundry integrates with external applications or where regulatory requirements make change management essential for certain projects. Would be great to get clarity on what Palantir and the development team recommend in these cases. Additionally, their perspective on the pros and cons of Project Roles versus Marketplace Installation Roles, and encouraged patterns.

From the diagrams you’ve shared, it appears that Marketplace Installation roles aren’t being used. When Marketplace Installation roles are in place, introducing a hotfix directly in project testing isn’t possible since they’re immutable. In that setup, the only viable path is to apply the hotfix in project dev, promote it to testing, and then to PROD. This is precisely why project testing exists, especially when external applications need to be orchestrated alongside the marketplace deployment.

Deploying into existing projects in Production mode while relying on project roles becomes messy quickly, and might not even be aligned with change management requirements. Developers inevitably and unintentionally introduce silent changes—sometimes even in PROD. On the next deployment, these changes are lost because they were never captured in DEV and end up being overridden. I cannot recommend this approach since it requires a high degree of discipline and it is easy to lose track.