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.

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

Make object storage and region configurable #42

Closed
karitra opened this issue May 11, 2022 · 1 comment · Fixed by #43 · May be fixed by #84
Closed

Make object storage and region configurable #42

karitra opened this issue May 11, 2022 · 1 comment · Fixed by #43 · May be fixed by #84

Comments

@karitra
Copy link
Contributor

karitra commented May 11, 2022

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

It possible to configure Yandex API endpoint, but storage endpoint bind to the constant in the source code, is it possible to allow customization of storage and region via configuration or, if supported by Yandex API, make it configurable via API calls? For first case I've modest patch, so would gladly post it as PR, if acceptable by code maintainers.

Use Case(s)

Use of Yandex packer plugin in custom/nonstandard environments with different storage endpoint and region settings.

Potential configuration

storage_endpoint: "storage.north-3.yandex-cloud.net"
storage_region: "ru-north-3"
@karitra
Copy link
Contributor Author

karitra commented May 11, 2022

It seems that according YandexCloud API docs it is possible to resolve Storage API endpoint via YandexCloud API call: https://cloud.yandex.com/en-ru/docs/api-design-guide/concepts/endpoints. It is placed within response with "storage" key.

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