- 
    
Bug
 - 
    Resolution: Done
 - 
    
Blocker
 - 
    1.7.0
 - 
    None
 
- 
        1
 - 
        False
 - 
        
 - 
        False
 - 
        Release Note Not Required
 - 
        
 - 
        
 
- 
        RHDH Plugins 3277
 
Description of problem:
When clicking plugin disable button, it doesn't disable plugin packages.
This is because frontend is calling:
PATCH /api/extensions/plugin/<namespace>/<name>/configuration/disable which will not work for plugins that do not have entry in the marketplace config, as it only updates plugin packages that are already in the config.
For newly added plugins to the marketplace config, one would need to call POST /api/extensions/package/<namespace>/<name>/configuration/disable for each its package.
It was decided it is the simplest to just update all plugin packages disabled when one calls PATCH /api/extensions/plugin/<namespace>/<name>/configuration/disable.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
# <steps>
Actual results:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Build Details:
Additional info (Such as Logs, Screenshots, etc):
- is related to
 - 
                    
RHDHBUGS-2094 Extensions: package disable not working correctly
-         
 - Closed
 
 -