Timeline for How to prevent accidental config changes made directly in Production?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2021 at 16:36 | history | edited | David at Experance Partners | CC BY-SA 4.0 |
added 19 characters in body
|
| Dec 16, 2021 at 11:22 | history | edited | David at Experance Partners | CC BY-SA 4.0 |
added 31 characters in body
|
| Dec 16, 2021 at 11:13 | history | edited | David at Experance Partners | CC BY-SA 4.0 |
added 31 characters in body
|
| Dec 16, 2021 at 5:42 | comment | added | Brent Bowers | I like the solution. Unfortunately we're the child company of an enterprise where browser extensions are tightly restricted and managed by the organization. | |
| Dec 16, 2021 at 3:21 | history | edited | David at Experance Partners | CC BY-SA 4.0 |
added second image
|
| Dec 16, 2021 at 3:18 | comment | added | David at Experance Partners | Also... I had to open PROD for the example above... the rest of the tabs were open. This points out the other important thought. WHY DO YOU NEED A PROD WINDOW OPEN? Close them. | |
| Dec 16, 2021 at 3:16 | history | answered | David at Experance Partners | CC BY-SA 4.0 |