This ticket has arisen from a Slack discussion [[https://wikimedia.slack.com/archives/C055QGPTC69/p1753809499666399|here]].
We noticed that blunderbuss is currently operating with the privileges of the `analytics` user on HDFS, since this is the kerberos principal that is defined within its keytab.
This configuration is less than ideal, since the `analytics` user has a lot more privileges than required. It could theoretically access PII, which is not a requirement of blunderbuss.
> ..the topic at hand is to somehow reduce the privileges that blunderbuss has today on HDFS, because we noted a privilege escalation to `analytics`.
> We want blunderbuss to have just the right amount of privileges to accomplish its current use case of landing files into the Airflow caches.
> ...it would probably be good for blunderbus to do that in a way that results in perms for the airflow instance admins to manage the artifact files if they need.
I think that we can use the `airflow-deployers` group, as defined [[https://github.com/wikimedia/operations-puppet/blob/production/modules/admin/data/data.yaml#L1149|here]], to ensure that those users with enhanced privileges in Airflow are able to manage the artifact files on HDFS.
We would need a system user for blunderbuss and for that user to be a member of this group.