...
To be able to remove the legacy deprecated code the first rule is to isolate it, and after the successfull isolation is to go to the chopping board and do the hard code removal.
Distributed Services
Diagram 1 - Using Gui Server
Embed draw.io Diagram |
---|
| |
---|
diagramName | ClientServer1 |
---|
includedDiagram | 1 |
---|
width | 891 |
---|
pageId | 138871171 |
---|
|
Diagram 2 - Using Legacy Clamp
Embed draw.io Diagram |
---|
| |
---|
diagramName | ClientServer2 |
---|
includedDiagram | 1 |
---|
width | 891 |
---|
pageId | 138871171 |
---|
|
Diagram 3 - No Middle Server
Embed draw.io Diagram |
---|
| |
---|
diagramName | ClientServer3 |
---|
includedDiagram | 1 |
---|
width | 771 |
---|
pageId | 138871171 |
---|
|
Login UI
Embed draw.io Diagram |
---|
| |
---|
diagramName | LoginUI |
---|
includedDiagram | 1 |
---|
width | 1201 |
---|
pageId | 138871171 |
---|
|
Known Issues
Multiple Logins for different applications.
Suggestions
Creating new Rest Endpoints - Either on Legacy Clamp or Gui-Server
...
Code Block |
---|
language | js |
---|
linenumbers | true |
---|
|
const response = await fetch('http://localhost:6969/onap/policy/clamp/acm/v2/instantiation', {
method: 'GET',
mode: 'no-cors',
credentials: "include",
headers: {
"Content-Type": "application/json",
Authorization: "Basic " + btoa('runtimeUser:zb!XztG34')
}
});
return response |
Distributed Services
...
Diagram 2 - Using Gui Server
...
Diagram 3 - No Middle Server
...
Login UI
...