-
Notifications
You must be signed in to change notification settings - Fork 72
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feat: Limit cnf_setup to only one CNF
Refs: #2095 - In attempt to set up a different CNF the user gets a warning and is blocked from proceeding. - There were some changes necessary in the ran_spec.cr tests to forego using two cnf_setups (auxiliary function was created to deploy 5g through helm instead). This should be changed in the future when cnf_manager.cr is rehauled. - This change also removes two spec tests that were considered unnecessary/non-conformant with the new approach to only having a single CNF set up at any given time. - Spec test to verify functionality was added.
- Loading branch information
Showing
4 changed files
with
56 additions
and
60 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters