Notifications

17 views

Description

The clone workflow maintains a hard coded preservation of all system properties starting with glide.email and glide.pop3 even if no preserver for those properties exists on the instance.

Steps to Reproduce

  1. On the target instance, remove the name starts with "glide.email" and name starts with "glide.pop3" conditions from the "Core Instance Properties" data preserver.
    2. On the target instance, modify the system properties with names starting with glide.email and glide.pop3.
    3. Request a clone.
    4. Once the clone is complete, verify on the target instance that the changes of the system properties have been preserved.

Workaround

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologize for any inconvenience.


Related Problem: PRB1236536

Seen In

SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - VR - Rapid7 - London 2019 Q2 v.6.2.1
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-09-12 08:35:17
Published:2019-09-12