When an existing field is set to required, related Permission Sets are not pulled

FabienTaillon commented 2 years ago

Describe the bug When an existing field is set to required, related Permission Sets are not pulled

To Reproduce Steps to reproduce the behavior:

Create a Scratch Org
Create a field (like a text field on Account)
Create a Permission Set and add read and edit access to the field
Pull everything
Go to the field and set it as required
Pull again

Expected behavior Both field and Permission Set should be pulled. Today, only the field is pulled, whereas the Permission Set should be pulled too. When deploying as is (without manually retrieving the Permission Set) you'll get this error: "You cannot deploy to a required field".

FabienTaillon commented 2 years ago

Case 42923165 created.

FabienTaillon commented 2 years ago

Known Issue created: https://trailblazer.salesforce.com/issues_view?id=a1p4V000002eKRcQAM

texei / sfdx-pull-issues

When an existing field is set to required, related Permission Sets are not pulled #6