Clean up code and fix issue with unknown resources
In companies, most of the time, we have test, stage and production environments.
It is very common that we, the developers, do not have the right to modify or touch the production directly because all the modifications must be traced in a versioning tool and tested before a production release.
However, a read access to the production (especially to the traces) can allow us to better understand a possible bug.
That’s why I propose this ZPM module that creates a new role in IRIS that allows access to the productions and this only in read-only with access to the visual traces.
This is a simple install of a new role : #Ready_Only_Interop.
The objective of this role is to visualize:
In a secure way, no action is permitted.
Open IRIS Namespace with Interoperability Enabled.
Open Terminal and call:
zpm "install readonly-interoperability"
You can have a demo of this role, from this git repository.
Use the user Viewer with password SYS.
Clone/git pull the repo into any local directory
$ git clone https://github.com/intersystems-community/iris-interoperability-template.git
Open the terminal in this directory and run:
$ docker-compose build
$ docker-compose up -d
Open the production.
With this link you will able to visualize but not modify any thing.
See traces : trace
Example :
The challange was from the SQL privileges to enable the message viewer.
This part was quiet tricky, because all the SQL privileges have to be promoted by hand of each Interoperabilty Namespace.