PULSE: Indicate/Config per Pulse Instance TO WHICH instances one can deploy
Is your feature request related to a problem? Please describe.
We have a DEV Pulse Instance and a PRD Pulse Instance do comply with SOX/Audit Controls We are allowed to on:
- On DEV Pulse Instance to migrate: DEV to DEV / DEV to UAT / PRD to UAT / PRD to DEV
- On PRD Pulse Instance to migrate: DEV to PRD / UAT to PRD
We are required to prove to the Auditors that our DEV Pulse Env can't Deploy TO PRD (However we need to use it to PULL from PRD to DEV/UAT, so it needs access to PRD but should not be allowed to PUSH)
Describe the solution you'd like
Per Pulse Instance, per model config (Where you specify Username & Password etc) have a tick box indicating if you can deploy TO that instance. Meaning, in DEV Pulse all DEV & UAT TM1 Instances will have the Deploy TO Ticket (Yes) but the PRD TM1 Instance won't have it Ticked (No). In PRD Pulse we will have only PRD TM1 instance Deployment Ticked (Yes) and all other env will have it set as No.
Its a similar Lookup config/check as the Approval but on a Target TM1 Instance level.
Describe alternatives you've considered
We will try to have our DEV Pulse only have READ Access to PRD TM1 Instance to see if that works (i.e. should be able to read existing objects but not overwrite), however that will cause our DEV Pulse not to see logs/threads etc of PRD TM1 Instance.
Additional context
Add any other context or screenshots about the feature request here.