libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SnailJie <>
Subject [GitHub] libcloud pull request #991: Add aliyun ecs instance join leave security grou...
Date Fri, 24 Feb 2017 00:53:39 GMT
GitHub user SnailJie opened a pull request:

    Add aliyun ecs instance join leave security group

    ## Changes Title (replace this with a logical title for your changes)
    ### Description
    Replace this with the PR description (mention the changes you have made, why
    you have made them, provide some background and any references to the provider
    documentation if needed, etc.).
    For more information on contributing, please see [Contributing](
    section of our documentation.
    ### Status
    Replace this: describe the PR status. Examples:
    - work in progress
    - done, ready for review
    ### Checklist (tick everything that applies)
    - [ ] [Code linting](
(required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](
    - [ ] [ICLA](
(required for bigger changes)

You can merge this pull request into a Git repository by running:

    $ git pull Add_AliyunECS_Instance_join_leave_security_group

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #991
commit 0acf45ec7dd1fddcca8a223ad1b7b2b76be75b99
Author: Jie Ren <>
Date:   2017-02-20T08:42:54Z

    Add join/leave security group methods for aliyun ECS

commit cc5921b7be12f27c8023bd520572c2a08a665139
Author: Jie Ren <>
Date:   2017-02-22T02:53:29Z

    Modify for CI test

commit 8d40de20fe529939e0d82ef26d85bc826b5b2e51
Author: Jie Ren <>
Date:   2017-02-23T01:00:58Z

    Modify for CI test


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message