Allow role permissions from yaml config

[tmaiaroto]

Allow role permissions from yaml config

[tmaiaroto]

Going to forget about this for now. The deploy command was updated to use managed policies instead of a custom inline policy for starters. Second, it will now also update the role it created. So if additional policies (managed or inline) are added in the future, the original role gets them.

So if a user defines their own role ARN in the config, it will be up to them to ensure it has all proper policies required. At this time, the goal of the deploy tool is not to be that comprehensive with regard to AWS resource management. There are already so many wonderful tools for that and nothing says that aegis can't be used alongside something like Terraform. One could manage all resources with Terraform and then simply provide a role ARN in the aegis config.

Though that said, there currently exists no way to use an existing API in the same manner one could use an existing role. So there's some overlap in concerns if a second tool was used to manage resources because the deploy command does manage some.

What would be better is a separate command for "upload" (or something) that might instead simply build upload the Lambda. It would skip all of the API creation, role creation/update, etc. It would assume one manually set all that up or used another tool.

...and I quite like the idea of aegis deploy for quick development and then something like Terraform for production where you want to keep infrastructure under revision control and do more. Perhaps tie into other things too. What Terraform lacks is the ability to build and upload the Lambda zip file. So maybe. A good possibility of a more bare bones upload command.

Still thinking about direction here...But the overall goal of aegis is to be light weight. So this falls outside current and foreseeable future goals.