fix: autoscaling disk_size_limit unit #1043
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Возникла ошибка. Пожалуйста, свяжитесь с администратором и укажите идентификатор запроса: 96467a9b-48a6-492c-a127-91817a6dff13 |
|
@MrKich, добрый день! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:
Несмотря на то, что в документации до этого было указано, что disk_size_autoscaling.disk_size_limit указывается в байтах - на практике провайдер принимает ГБ.
Если указать байты, например 100000000000 для 100 Гб, то при прокатке появится ошибка вида
max disk size value must be more than 0.Это скриншот, если в UI создать кластер с макс. размером в 100 гб и попытаться в терраформе указать в байтах.
