In the case of creating custom plugins (i.e. Password Encryptors). Those are required to be placed inside the plugins folder before starting FusionAuth. Since cloud containers need to be stateless, these plugins need to exist in the container image from the first place. Which is not currently supported by FusionAuth.
Solution
Adding a new plugins property to the kickstart file. One that accepts an Array of plugins (i.e. relative paths) to be auto-copied into FusionAuth at build time. Another option would be to support a URL to copy the .jar file from into the plugin directory.
Alternatives/workarounds
Applying custom modifications to FusionAuth Dockerfile for manually copying custom plugins into FusionAuth before reaching the container entry point.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
Auto-install custom plugins via kickstart
Problem
In the case of creating custom plugins (i.e. Password Encryptors). Those are required to be placed inside the
plugins
folder before starting FusionAuth. Since cloud containers need to be stateless, these plugins need to exist in the container image from the first place. Which is not currently supported by FusionAuth.Solution
Adding a new
plugins
property to the kickstart file. One that accepts an Array of plugins (i.e. relative paths) to be auto-copied into FusionAuth at build time. Another option would be to support a URL to copy the .jar file from into theplugin
directory.Alternatives/workarounds
Applying custom modifications to FusionAuth Dockerfile for manually copying custom plugins into FusionAuth before reaching the container entry point.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.