Hi, A follow up on that. The story for the sprint has been finally achieved. It took me far more time than expected but the feature is usable and support only Gerrit resources.
I won't work more on it until patches are checked and approved. All patches are in the following Gerrit topic: http://softwarefactory-project.io/r/#/q/topic:git_style And the dependency order is as follow: - http://softwarefactory-project.io/r/#/c/4608/ - http://softwarefactory-project.io/r/#/c/4888/ - http://softwarefactory-project.io/r/#/c/5052/ - http://softwarefactory-project.io/r/#/c/5135/ - http://softwarefactory-project.io/r/#/c/5150/ - http://softwarefactory-project.io/r/#/c/5208/ - http://softwarefactory-project.io/r/#/c/5218/ A SF can be built with those changes by preparing /var/lib/sf/deps/managesf with the review 5208 and software-factory with review 5218. $ DEBUG=1 MANAGESF_KEEP=1 ./run_functional_tests.sh Once deployed the user can submit and approved changes inside config/resources/ by following the expected format. Creation, Deletion and Update of resources are supported (only on Gerrit). Here is an example of a yaml resources file that can be submitted: ====== resources: projects: ichiban-project: name: ichiban-project description: An awesome project contacts: - [email protected] source-repositories: - ichiban-client - ichiban-server website: http://ichiban-cloud.io documentation: http://ichiban-cloud.io/docs issue-tracker: http://ichiban-cloud.bugtrackers.io repos: ichiban-server: name: ichiban-server description: The server part acl: ichiban-project-acl ichiban-client: name: ichiban-client description: The client part acl: ichiban-project-acl acls: ichiban-project-acl: file: | [access "refs/*"] read = group Anonymous Users read = group ichiban-core owner = group ichiban-ptl [access "refs/heads/*"] label-Code-Review = -2..+2 group ichiban-core label-Verified = -2..+2 group ichiban-ptl label-Workflow = -1..+1 group ichiban-core submit = group ichiban-ptl read = group Anonymous Users read = group ichiban-core [access "refs/meta/config"] read = group ichiban-core [receive] requireChangeId = true [submit] mergeContent = false action = fast forward only groups: - ichiban-ptl - ichiban-core groups: ichiban-ptl: name: ichiban-ptl members: - [email protected] ichiban-core: name: ichiban-core members: - [email protected] - [email protected] ==== Any manual tests and feedback would be greatly welcome. Additionally /usr/local/bin/resources.sh have an argument called "direct_apply" that let an operator bypass the (review+config-check+config-update) process to create/update/delete resources. This can be used later in the functional test to speedup resources operation ops. Note the default config repository, groups and acl are created through this new resources managesf direct_apply endpoint. I hope we will be able to merge that quickly to avoid annoying rebasing / retesting. As following tasks, I'm thinking about: - Investigate how to integrate Storyboard - Write the documentation operator and user -- Auto generate the resources doc based on each resource description - Try the de-activation of legacy project/groups/memberships endpoint via the policies - Document the migration process - Add a OperatorGroup resource where members we be part of the Gerrit Administrator group (storyboard Administrator Group if any, same for the other services). Also member will have their ssh pub key added to the node .ssh/authorized_keys). - Propose a SF Welcome page that list the project resources and give the information details about them (this to replace our current one) - Can be nice also to revamp the SF-Pages via this GIT style resources definition and have a resource SFPages that have two config keys: page-path and deploy-key: (pub key). -> Will require something to authorize only the deploy key to push files under a specific directory (apache-root/pages/<page-path>/.) Cheers, Have a good WE. Fabien Le 24/10/2016 à 16:53, Fabien Boucher a écrit : > Hi, > > As this is a bunch of code for the resource GIT style I don't want > we wait to much before having them reviewed and hopefully approved. > > Please have a look : > > In the order of merge priority: > > - http://softwarefactory-project.io/r/#/c/4608/ (CR+2 by Tristan) waiting for > another one or let me know if I can +1V > - http://softwarefactory-project.io/r/#/c/4888/ > - http://softwarefactory-project.io/r/#/c/5052/ (Approved but depends on ^) > > After: > > - http://softwarefactory-project.io/r/#/c/5135/ > - http://softwarefactory-project.io/r/#/c/5150/ > > Cheers, > Fabien > _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
