Controlled access to /announcements route path

[sharadpattanshetti]

Hi,
We are trying to integrate this plugin with our backstage announcement. WE want to keep the access to /announcements route path limited to only certain team (kind:group).
Has anyone tried this or any suggestion on how this can be achieved?

[DanKreck]

The easiest way to do this is to create a permission policy to check if the user belongs to that group. This plugin makes it available via announcementCreatePermission, announcementDeletePermission, and announcementUpdatePermission. This would allow everyone to see the announcements but only your defined group would see the edit, delete, and create buttons. Navigating to announcement/create would return a 404.

[sharadpattanshetti]

Sure @DanKreck I will try it out. However, I am able to integrate and get plugin working in my local backstage instance but when I deploy it to our Kubernetes cluster it throws below error. Also, the application fails to come up.
Any hints or suggestions on what could be wrong? (we are on backstage v1.10)

stderr F /usr/share/nginx/html/static/module-k-phoen.a0ce6ac3.js: No such file or directory

Other Errors in log are:

stdout F {"level":"warn","message":"Task worker failed unexpectedly, attempt number 2, Error: connect ECONNREFUSED