1. merge skyline-policy-manager into skyline-apiserver
2. move tests into skyline-apiserver
3. we will remove skyline-policy-manager after we merge
skyline-nginx into skyline-apiserver
Change-Id: Id57598f3726c891e399af81eb0383746f78386b5
1. update policy for manila, use role instead of rule
2. update policy for trove, use role instead of rule
3. update the dependencies for skyline-policy-manager
Change-Id: I57f010f769575f7b75673c5c154eac4fed07b708
1. Move skyline-apiserver to libs
2. Modify Makefile
3. Rename the skyline-apiserver.yaml.sample file to skyline.yaml.sample
At the top level, we use "skyline" as the namespace, using the idea of
monorepo to manage the project. At the top level, only some common
configuration files (mypy.ini, black.conf, isort.conf, etc.) and
common tools are included.
In the `libs` directory, there are three core libraries,
skyline-console, skyline-apiserver, skyline-nginx, and some dependent
libraries.
There are cross-imports between these libraries,
for example: skyline-nginx requires skyline-apiserver;
Both skyline-nginx and skyline-apiserver require skyline-config.
Therefore, skyline-apiserver should not be placed
at the top level, it is also suitable for management as a library.
Change-Id: Ie2f1f4bdfbc2e985ec4327705eecaae3181f5b50
1. add a cmd script to generate sample config
2. set setup as False for generate_swagger, so we can make swagger
without skyline-apiserver yaml config
3. add make genconfig into Makefile
4. add config-sample-generator scripts into pyproject.toml
5. replace async with sync for generate_swagger script
6. add items, keys, values function for Group and Configuration
Change-Id: I4c7196f1d766a6abdc24c71c4b3135cd40cc26ef
