Potential Composer & SSH issues with module install/update/uninstall
This is untested so far, however there is a theoretical issue I can see here:
During the build of the image, apiopenstudio_stage_1
is purposefully separated from apiopenstudio_stage_2
so that SSH keys are not revealed and during apiopenstudio_stage_2
the .composer
directory is removed from /root/
for image size reasons.
However, the admin docker will need to use API calls that utilise bash git commands to install plugins and processors, as will bin/aos-modules
.
Composer functionality (and therefore SSH keys) needs to be maintained without compromising security.
Suggestions:
- Implement another
--mount
command to allow the user to use their own server keys within the image, do not delete/root/.composer
. Q: will there be a permissions issue, will composer still work when using different keys as those from the initial image build?