Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(service): switch from http to https #56

Draft
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

scott-howe-1
Copy link
Collaborator

cfm-service needs to change from using http to https.
This PR will switch all 3 cfm components (service, webui, cli) at the same time, to avoid any confusion\conflicts.

At this PR's creation, only service and cli have been switched to using https. The webui still needs to be done. This PR will remain as a "Draft" until that action is complete. Once complete, the PR can go into main and complete the switch to https.

The same error handling code is copy-pasted all over the backend.  Consolidate this code in 1 common error handler function so it's easier to update next time.
Then, fixed the code that's not handling non-cfm-service errors correctly.
Also, need to fix potential memory leaks that come from NOT using "defer response.Body.Close()" after a call into cfm-service.
The service provide a self-signed certificate file (.crt) so clients can use secure.  Insecure is also available.
scott-howe-1 and others added 8 commits December 2, 2024 15:30
…nd update (#57)

* refactor(cli): command usage and example string generation refactor and update

* doc(cli): add docker-specific note about service-related cli options
* feat: set the nodes width based on the device id dimensions

* feat: add ipaddress to the existed devices in dashboard

* feat: add new button to discover new devices and the related interfaces

* fix: fix the bug in addDiscoveredHosts interface

* fix: fix bug in addDiscoveredBlades interface

* feat: add function addDiscoveredDevices with output popup and waiting popup

* style:  separate lines for discovered blades and hosts

* feat: add waiting progress for device discovery

* feat: update the content after adding new discovered devices

* feat: distinguish node status by border color

* feat: prevent the user from manually adding blades to the CMA_Discovered_Blades appliance

* style: remove unnecessary stype setup
…e using privileged mode (#60)

* feat: update the docker running command to make D-bus available ay priviledged mode

* fix: update the docker running command to make D-bus available using privileged mode
Found a couple bugs in appliance.AddBlade() and manager.AddHost().
(1) corner case where an empty bladeId is being allowed, when it shouldn't
(2) Not enough information is being saved to new blade objects during error handling.  This was causing a panic during the delete because the backendOps variable was a nil point being used to call a backend function.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants