stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dinithis <>
Subject [GitHub] stratos pull request: 4.1.0 beta deployment policy fix
Date Wed, 18 Feb 2015 06:47:22 GMT
GitHub user dinithis opened a pull request:

    4.1.0 beta deployment policy fix


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

    $ git pull 4.1.0-beta-deployment-policy-fix

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 #232
commit 9b5288e97429dd46377e348c40a23d9a64114b54
Author: Dinithi <>
Date:   2015-02-16T09:39:15Z

    CLI commands added for adding and updating deployment policies.

commit 828c49dc99c5ee883a60c019c759f096da254579
Author: Dinithi <>
Date:   2015-02-16T10:11:46Z

    removeDeploymentPolicy API method updated

commit 3b462f393e05edd0453fa61ff5a778b7a1517321
Author: Dinithi <>
Date:   2015-02-16T11:42:01Z

    CLI command added to remove Deployment Policy.

commit d1268ce911e4ed12907b445e4d5a4ee272cf1173
Author: Dinithi <>
Date:   2015-02-16T13:05:22Z

    Merge branch '4.1.0-beta-deployment-policy-fix' of into

commit 5a393e29aadd20a4f5fe20585675728d5163c8f7
Author: Dinithi <>
Date:   2015-02-16T13:09:05Z

    removed unnecessary CLI constants

commit d6ec69527f95bb495fb8abb70526f0c1bdb35b52
Author: Dinithi <>
Date:   2015-02-17T04:30:20Z

    Merge branch '4.1.0-beta-deployment-policy-fix' of into

commit a0cefe71f4ade70ac28fc14920087db42664dee6
Author: Dinithi <>
Date:   2015-02-18T06:37:04Z

    response code checking condition changed for undeployEntity method

commit 5b34c95369c345d48b01b4a0ec0b90854a6582c1
Author: Dinithi <>
Date:   2015-02-18T06:41:49Z

    Merge branch '4.1.0-beta-deployment-policy-fix' of into


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