ike thecoder

**Technical Design Option 2** Add an "Integrations" to the Namespace page, where a user will be able to (1) establish relationship with another Organization Namespace, and (2) request access ...

@Jonesy Tested in "test" environment and it is still showing as a button for unauthenticated users.. 

Logging: ``` verbose: [notification.service] Notification triggered verbose: [notification.service] Notification triggered verbose: [notification.service] Notification triggered verbose: [notification.service] Notification triggered debug: [keystone.access-req] Mutation [markAccessRequestAsNotIssued] result {"data":{"updateAccessRequest":{"id":"267"}}} debug: [keystone.activity] [recordActivity] userid=272 name=update AccessRequest[267]...

Although this is an error, it is a very boundary case, so I am going to label as `wontfix` but if we have free cycles we could look at later.

Should it be the Email and Name of the Access Manager that rejected the request?

@Jonesy were you able to confirm if this issue is still relevant?

Adding to Epic #155 as it is to do with the API Directory redesign.

No longer blocked by Hierarchical Access Management

Although this is an error, it is a very boundary case, so I am going to label as wontfix but if we have free cycles we could look at later.

Hi @WadeBarnes I was reluctant to create a separate image specifically for the backup-container - those scripts under "/patroni-spilo/root/" are not part of the Spilo base image, they are only...