Question on Profile Deployment

[sameerseekala1]

How will 'sgd:source:delta' command work on profiles? If we make 1 FLS change on the profile file with it generate delta with only that specific change or it shows entire profile file? I tried to test it but every time it shows all the page layout assignments along with the FLS change in the profile.
Please let me know how the command works for profiles TIA.

[scolladon]

Hi @sameerseekala1 !

You are not alone facing this particular behavior of the plugin
Here is an issue logged a few days before you here

I tried to answer there, feel free to raise any remaining questions

[sameerseekala1]

hi @scolladon,
How does this plugin work on permission sets? I added a change to a PS but the delta is creating a PS file with all the changes. Is this expected? Please advice.

[scolladon]

Hi @sameerseekala1,

Permission Sets are treated differently by the metadata API.
When a permission set is deployed, its content during the deployment define its content in the org.
It means it is not possible to do partial deployment with permission set.

You can verify that very easily:

1. Create a PSet with FLS on 2 fields on the Account object
2. Retrieve this PSet via sfdx
3. Remove one FLS from the file
4. Deploy the PSet
5. Check in the org, the PSet has now only one FLS configured.

[sameerseekala1]

Thanks @scolladon.
Just want to check on a different topic, what is the best way to do backup job using Github Actions? We want to backup our prod into master branch daily so is this possible in Github Actions? Is there any predefined action in Marketplace or a plugin that does the job, please suggest.

[scolladon]

I do not have encountered this use case.
What I would do is just use git labels with a date pattern.
I think it is possible to create a schedule workflow with github action to do that

[sameerseekala1]

Thanks @scolladon will give a try.