Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Copy object instead of deploy the object from local env #5

Closed
victorshinya opened this issue Jul 11, 2020 · 1 comment · Fixed by #6
Closed

Copy object instead of deploy the object from local env #5

victorshinya opened this issue Jul 11, 2020 · 1 comment · Fixed by #6
Assignees
@victorshinya
Labels
enhancement New feature or request

Comments

@victorshinya
Copy link
Contributor

The current process is: download the object, parse the JSON, send to the LogDNA, upload the object, and delete the object. For IBM Cloud users, you can use the Private Endpoint to avoid any Public Bandwidth cost, but for those who are not using IBM Cloud, it can generate an extra charge.

So, to improve the process, the function should be able to copy the object instead of deploying the local one.
@victorshinya victorshinya added the enhancement New feature or request label Jul 11, 2020
@victorshinya victorshinya self-assigned this Jul 11, 2020
@victorshinya victorshinya linked a pull request Jul 11, 2020 that will close this issue
Copy object and remove #6
Merged
@victorshinya
Copy link
Contributor Author

Solved by PR #6

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

@victorshinya victorshinya

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Copy object and remove victorshinya/ibm-logdna-cos
1 participant
@victorshinya