[
https://issues.apache.org/jira/browse/CLOUDSTACK-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521858#comment-14521858
]
ASF subversion and git services commented on CLOUDSTACK-8433:
-------------------------------------------------------------
Commit bb0d978ce3f6405b3b08c971aa6dbbd271a44a59 in cloudstack's branch
refs/heads/nuke-awsapi from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bb0d978 ]
CLOUDSTACK-8433: remove awsapi db usage, fix upgrade cleanup and fix packaging
- Removes awsapi db properties usage across codebase
- Removes references from spring xmls, test cases and TransactionLegacy
- Adds sql command to drop database cloudbridge in schema-451to460-cleanup.sql
- Removes commons-logging.properties file introduced with awsapi
- Fixed utils to use log4j instead of commons logging
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> Deprecate and remove CloudStack AWSAPI which is not actively maintained or
> widely used
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8433
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8433
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.6.0
>
>
> Since the last discussion on dev ML, I've tested awsapi on ACS 4.5 and it
> does not work for me, possibly due to using older versions while newer
> clients such as awscli have moved now. I tried ec2stack which worked out of
> the box. It only makes sense to deprecate awsapi, remove it and add an
> upgrade path starting 4.6.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
