Allow all users to read RabbitMQ credential to get notifications
Needs ReviewPublic
Actions

Authored by dereckson on Oct 16 2024, 20:47.

Tags

None

Referenced Files

	Unknown Object (File)
	Sun, Jan 26, 08:15

	Unknown Object (File)
	Fri, Jan 24, 01:49

	Unknown Object (File)
	Tue, Jan 14, 05:51

	Unknown Object (File)
	Tue, Dec 31, 01:33

	Unknown Object (File)
	Tue, Dec 31, 01:29

	Unknown Object (File)
	Mon, Dec 30, 21:38

	Unknown Object (File)
	Mon, Dec 30, 21:37

	Unknown Object (File)
	Mon, Dec 30, 21:07

View All 47 Files

Subscribers

None

Details

Reviewers

aceppaluni

Summary

The RabbitMQ credential for notifications is intended to be shared
among devserver users, as such, it makes sense to make the secret
file readable for the nasquenautes group.

This credential allows only to READ from a queue on the dev vhost,
and doesn't give access to anything else than notifications.

Test Plan

Deployed on WindRiver

Diff Detail

Repository

rOPS Nasqueron Operations

Lint

Lint Passed

Unit

No Test Coverage

Branch

notifications-nasquenautes

Build Status

Buildable 5599
Build 5881: arc lint + arc unit

Event Timeline

dereckson requested review of this revision.Oct 16 2024, 20:47

dereckson created this revision.

Harbormaster completed remote builds in B5599: Diff 9060.Oct 16 2024, 20:47

dereckson added inline comments.Oct 16 2024, 20:47

roles/devserver/userland-software/notifications.sls
33	This is always deployed to devservers, as this is a part of the devserver role.

Revision Contents
Changeset List

Path

Size

roles/

devserver/

userland-software/

notifications.sls

4 lines

Diff 9060

View Options

roles/devserver/userland-software/notifications.sls

Allow all users to read RabbitMQ credential to get notificationsNeeds ReviewPublicActions