alias deployments with function level roles/custom IAM roles don't work the same as core Serverless (Serverless empowers you to define custom roles and apply them to your functions on a provider or individual function basis). lambdaRole will use the currentRoles only if a provider role is present.
My service is setup to use the Cloudformation import value function for setting a KMS decryption role on a function. This role is an output of another stack (role: { "Fn::ImportValue": "KmsDecryptRoleName${self:custom.stage}" }). Without the alias plugin, the function gets the correct role and the rest of the functions get the default (Serverless generated) role.
After reading the code, I'm using a workaround of setting the role on the provider, however It's really only necessary on the one function.
alias deployments with function level roles/custom IAM roles don't work the same as core Serverless (Serverless empowers you to define custom roles and apply them to your functions on a provider or individual function basis). lambdaRole will use the currentRoles only if a provider role is present.
My service is setup to use the Cloudformation import value function for setting a KMS decryption role on a function. This role is an output of another stack (role: { "Fn::ImportValue": "KmsDecryptRoleName${self:custom.stage}" }). Without the alias plugin, the function gets the correct role and the rest of the functions get the default (Serverless generated) role.
After reading the code, I'm using a workaround of setting the role on the provider, however It's really only necessary on the one function.