This adds the option to configure Artemis users with credentials and roles.
An additional init-container has been introduced to populate the required artemis-users.properties and artemis-roles.properties files, joining user/role settings from helm values with the respective passwords from individual secrets.
:information_source: Currently the passwords are stored in plaintext inside the containers.
:information_source: This still works with the ARTEMIS_USERNAME & ARTEMIS_PASSWORD environment variables. If they are set, they have higher priority.
Testing notes: I verified that it's possible to configure a user with role amq and that it's possible to login to the management console with that user at http://localhost:8161/console. In the future, it should probably be possible to further customize the permissions per roles.
DI note: The structure of the users helm-values-map should enable us to use this with our k8s secret provisioner.
This adds the option to configure Artemis users with credentials and roles.
An additional init-container has been introduced to populate the required
artemis-users.propertiesandartemis-roles.propertiesfiles, joining user/role settings from helm values with the respective passwords from individual secrets.:information_source: Currently the passwords are stored in plaintext inside the containers.
:information_source: This still works with the
ARTEMIS_USERNAME&ARTEMIS_PASSWORDenvironment variables. If they are set, they have higher priority.Testing notes: I verified that it's possible to configure a user with role
amqand that it's possible to login to the management console with that user at http://localhost:8161/console. In the future, it should probably be possible to further customize the permissions per roles.DI note: The structure of the
usershelm-values-map should enable us to use this with our k8s secret provisioner.