infrastructure
/
meta
7
0
Issues 51 Pull Requests Projects 5 Releases Activity

[Mattermost] Lock down and define policy for Mattermost Services #66

New Issue
Open
opened 2024-03-26 07:06:51 +00:00 by label · 1 comment
label commented 2024-03-26 07:06:51 +00:00
Owner
Copy Link

Mattermost Services should be setup on a per-request basis. There are currently too many notifications/bots/service accounts being created and/or generated without the knowledge beforehand of Infrastructure. This indicates not only permissions/roles need to be adjusted, but it also indicates that expectations also need to be set on how a service should be requested, setup, or exist in the first place in our instance.

Mattermost Services should be setup on a per-request basis. There are currently too many notifications/bots/service accounts being created and/or generated without the knowledge beforehand of Infrastructure. This indicates not only permissions/roles need to be adjusted, but it also indicates that expectations also need to be set on how a service should be requested, setup, or exist in the first place in our instance.
label added the
component/mattermost
 label 2024-03-26 07:06:51 +00:00
label self-assigned this 2024-03-26 07:06:51 +00:00
neil was assigned by label 2024-03-26 07:06:51 +00:00
tgo was assigned by label 2024-03-26 07:06:51 +00:00
label added this to the RESF Infrastructure Stability and Maintenance project 2024-03-26 07:06:51 +00:00
label added the
issue
priority
high
 labels 2024-03-26 07:07:07 +00:00
brian commented 2024-03-26 09:46:49 +00:00
Member
Copy Link

Ah, a few of those are my fault. I’ll go through the list and clean up the webhooks I no longer use / etc.

Ah, a few of those are my fault. I’ll go through the list and clean up the webhooks I no longer use / etc.
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
Clear current reference
Labels
Clear labels   
bug

Something is not working

  
component/ansible

   
component/git

   
component/idm

   
component/mattermost

   
component/mirrors

   
duplicate

This issue or pull request already exists

  
effort
high

  
effort
low

  
effort
medium

  
enhancement

New feature

  
gain
high

  
gain
low

  
gain
medium

  
help wanted

Need some help

  
invalid

Something is wrong

  
issue

   
needinfo

More information is needed

  
permissions
  
priority
high

  
priority
low

  
priority
medium

  
task

   
wontfix

This won't be fixed

No Label
bug
component/ansible
component/git
component/idm
component/mattermost
component/mirrors
duplicate
effort
high
effort
low
effort
medium
enhancement
gain
high
gain
low
gain
medium
help wanted
invalid
issue
needinfo
permissions
priority
high
priority
low
priority
medium
task
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
RESF Infrastructure Stability and Maintenance
Assignees
Clear assignees
No Assignees
label
neil
tgo
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/meta#66
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?