This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Deploying Apps (ProfileActionOverrides) and Profiles (Default App) #1258
Labels
analysis
To be decided on how to solution/fix
Describe the bug
Currently it is hard to deploy apps with ProfileActionOverrides and profiles with default app. Both currently require dummy metadata to be put into the repository.
Apps in src-ui may depend on profiles, so profiles must exist in the target org before they are deployed. And apps and their dependent profiles can’t be deployed together as well.
Reconcile doesn’t work in this case because there are no profiles in src-ui, and src-access-mgmt is deployed later. T
Also, not all metadata can simply be packed into one package.
Following possible solutions:
Idea 1:
Either dummy profiles can be placed on a preliminary source package. The Profile Package would then have to be set to always Deploy. If the dummy profiles were deployed without the complete profiles, the profiles would be set completely to the dummy profiles.
Idea 2:
Add an app reconcile. Place the applications and profiles in the same package. When deploying, create a dummy app for each existing app in the current package. When the trimmed down profiles are deployed, the dummy apps are also deployed.
After that, we have a trimmed down application and a trimmed down profile.
Now we can deploy the full profile and the full application because the two dummies are already available.
Idea 3:
Either dummy profiles can be placed on a preliminary source package, or a predeployment script on src-ui can create and deploy dummy profiles on the fly.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Platform Details (please complete the following information):
Additional context
Dummy app:
The text was updated successfully, but these errors were encountered: