New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CloudWatch Logs support #616

Closed
jimberlage opened this Issue Sep 4, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@jimberlage
Contributor

jimberlage commented Sep 4, 2014

I see that in the aws-sdk-core you have CloudWatch Logs on the roadmap. Your CONTRIBUTING.md states that we should ask about significant requests, so... Would you be willing to accept a pull request here with that functionality? It's something which would be extremely useful in the current SDK.

@trevorrowe

This comment has been minimized.

Show comment
Hide comment
@trevorrowe

trevorrowe Sep 4, 2014

Member

The aws-sdk-core gem actually supports the CloudWatch Logs API today.

require 'aws-sdk-core'
cwl = Aws::CloudWatchLogs::Client.new
cwl.operation_names
#=> [:create_log_group, :create_log_stream, :delete_log_group, ...] 

You can safely run aws-sdk v1 and aws-sdk-core in the same process/application without conflict. Is there a particular reason you would like to see this backported?

Member

trevorrowe commented Sep 4, 2014

The aws-sdk-core gem actually supports the CloudWatch Logs API today.

require 'aws-sdk-core'
cwl = Aws::CloudWatchLogs::Client.new
cwl.operation_names
#=> [:create_log_group, :create_log_stream, :delete_log_group, ...] 

You can safely run aws-sdk v1 and aws-sdk-core in the same process/application without conflict. Is there a particular reason you would like to see this backported?

@jimberlage

This comment has been minimized.

Show comment
Hide comment
@jimberlage

jimberlage Sep 5, 2014

Contributor

Thanks for the explanation, if they can be used without conflict I'll simply use both. I have no need for a backport, then.

Contributor

jimberlage commented Sep 5, 2014

Thanks for the explanation, if they can be used without conflict I'll simply use both. I have no need for a backport, then.

@jimberlage jimberlage closed this Sep 5, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment