•  
     
    story #10218 manage "default layout" with REST API
Summary
Empty
manage "default layout" with REST API
Empty

This apply only for repository creation so only POST route is affected:

POST /svn

{
    ...
    "settings": {
        "commit_rules": {
            "mandatory_reference": boolean,
            "allow_commit_message_change": boolean
        },
        "access_file": [
            "[/]",
            "* = ",
            "Contributors = r",
            "[/stuff]",
            "Contributors = rw"
        ],
        "immutable_tags": {
            "paths": [
                "/tags"
            ],
            "whitelist": [
                "/tags/moduleX"
            ]
        },
        "email_notifications": {
            [
                {
                    "path": "/trunk",
                    "user_groups": [
                        {
                            "id": "101_3"
                        },
                        UserGroupRepresentation
                    ],
                    "users": [
                        {
                            "id": 333
                        },
                        UserRepresentation
                    ],
                    "emails": [
                        "foo@example.com",
                        string
                    ]
                }
            ]
        },
        "layout": [
            "/trunk",
            "/tags",
            "/branches",
            "/branches/moduleX"
        ]
    }
}
  • layout will create listed directories as "Revision n°1" of the repository
  • Only folders are created, it's not possible to create files
  • If the given layout cannot be created there is no error returned but the corresponding system event will be marked as "Warning"
  • The layout is created in 1 commit, this means that it's "all or nothing", if something prevent the the creation of one path or the whole commit it self, nothing will be created
  • The commit is author is the user who made the REST call.

 

Empty
Thomas Gerbet (tgerbet)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#10218
Manuel Vacelet (vaceletm)
2017-08-01 13:16
2017-05-15 11:58
3278

References

Follow-ups

User avatar
Thomas Gerbet (tgerbet)2017-07-25 15:43
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Status changed from Ready (stalled) to On going
  • CC list set to Thomas Gerbet (tgerbet)
  • Permissions set to