I have created an unlocked package. The unlocked package contains named credential. The unlock package process creation when failed when there was no in the file.
So, I had to add actualPassword in the package. With this, I did create an unlocked package successfully and installed in an org.
I can see the deployed named credential, however the issue is I have to edit named credential and update password manually.
Doesn't the password that was added in the *namedCredential file gets automatically inserted when unlocked package is deployed in an org.
Is this behavior same in managed package as well? I have not tried but heard that managed package deployment will add named credential password as well (without user having to edit the password manually)