stelligent
Public extensions, private extensions, support artifacts
Plan to create:
Public extensions: Uses native AWS services, might be too much effort to include in mu core
Private extensions: May use non-native AWS services, requires IAM roles/permissions
Support artifacts: examples would be source files, Dockerfiles, buildspecs, etc.
Side note*: Anything in mu core will be AWS native
For more info about mu extensions: https://github.com/stelligent/mu/wiki/Mu-Extensions
I want to capture original idea behind how to implement private extensions:
Currently you can use s3://... urls for the extensions and this will require the mu caller to be running as an IAM user/role with access to that S3 object.
Currently you can use s3://... urls for the extensions and this will require the mu caller to be running as an IAM user/role with access to that S3 object.
@cplee Just a matter of documenting it?
