Group-based permissions & finer-grained authentication about datacube-core HOT 3 CLOSED

Need to be a bit careful with the AAA design for AGDC. We have HPC, Cloud and PC targets and multiple deployment environments (e.g. NCI, Pawsey, AWS (CEOS Data Cube)). The technology stack shouldn't be hard wired in a way that prevents the variety of target environments from working.
Postgres authentication will probably be fine in all cases, but I'm no expert and just wanted to highlight the requirement here isn't just for the specific NCI deployment environment.

from datacube-core.

Good point Rob.

From the perspective of AGDC's code, this will only hard-code the Postgres roles expected not the authentication scheme.

The authentication scheme used is dependent on the deployment of the Postgres server. An environment can always use manually-configured users, as with AGDCv1.

from datacube-core.

• AGDC roles are now created on database initialisation
• We've added cli grant commands to add/modify users
• Our NCI modules now use NCI usernames instead of cube_user.

Closing.

from datacube-core.