We are currently doing some testing to see if Juju will fit our needs to deploy a new application to EC2. We have three developers that need to be able to make changes to the the deployed instances, but . . .
. . . right now, only the person that bootstrapped juju is the only one who can make changes. Obviously this doesn't work out very well.
We are aware of the authorized-keys-path and the authorized-keys settings for the environments.yml files, but can't seem to get them to work correctly. How are they supposed to be setup in order to allow multiple people to administer the deployed instances?