Age | Commit message (Collapse) | Author | Files | Lines |
|
* Add a liquibase change set to update cps ran model data
* Rename model "cps-ran-schema-model@2021-01-28.yang" to
be compliant with yang specifications related to file layout
https://tools.ietf.org/html/rfc7950#section-5.2
* Improve yang validation error handling to provide more information
about the validation failure in the request response
* Add csit test to verify cps ran model retrieval
Issue-ID: CPS-377
Signed-off-by: Bruno Sakoto <bruno.sakoto@bell.ca>
Change-Id: I4f0e337b50d79e81f895eb32f09ae9cb5d9d8a70
|
|
- Undo (accidental) changes in orginal liquiubase cahnge set (03)
(see commit : https://gerrit.onap.org/r/c/cps/+/119061)
- Add new changeset for required changed related to checksum calcualtion
- There is a incorrect field name (checkstyle instead of checksum) in 03-loadData-schema-set.yaml
but it seems to be ignored/overruled by the .csv import. If we change it liquibase report an checksum error during upgrade
i.e were are not allowed to touch the file!
Issue-ID: CPS-310
Signed-off-by: ToineSiebelink <toine.siebelink@est.tech>
Change-Id: I00c94e3f1ddab7c9c54aac1294019ec7cd51634f
|
|
This change deletes the database index on fragment table for dataspace
and xpath.
Issue-ID: CPS-300
Signed-off-by: Bruno Sakoto <bruno.sakoto@bell.ca>
Change-Id: I586cc38f7ed00a16f751ed4dbe3b514226c62657
|
|
https://sonarcloud.io/project/security_hotspots?id=onap_cps&hotspots=AXfObcurA2pnU4Plp4-j
Issue-ID: CPS-286
Signed-off-by: puthuparambil.aditya <aditya.puthuparambil@bell.ca>
Change-Id: I31012f81797396682dbccae0e4992a33bac806c7
|
|
+ also fixes issue with fragment_id sequence not reflecting data loaded
Issue-ID: CPS-261
Change-Id: If590d6a0859a1acc9005dd2da952b7dd93a23059
Signed-off-by: Ruslan Kashapov <ruslan.kashapov@pantheon.tech>
|
|
1. Common change-log master used only to specify the different change sets.
2. Specific change set created for cpsTables creation and for loading data to each cps component like dataspace, schema-set, anchor and dataNode
3. The data load cabability is configurable in the sense, it will be trigered only if the label is specified in the application.yaml
Issue-ID: CPS-173, CPS-242
Signed-off-by: puthuparambil.aditya <aditya.puthuparambil@bell.ca>
Change-Id: I44c640ce50b7203f5799d722149397478a98bc05
|