-
Notifications
You must be signed in to change notification settings - Fork 117
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
ecs charge type issue #320
Comments
terraform alicloud provider only support "PostPaid" instance now |
Hi @henry-zhang I am sorry for that. I have released version 1.5.0 and it fixed above error. Please update it. After updated, you can specify new field 'period_unit', and it support 'Month' and 'Week'. Thanks a lot. Hi @bittopaz terraform alicloud provider always supports 'PrePaid'. Besides, the latest version version 1.5.0 has supported to change 'PostPaid' to 'PrePaid', and welcome to update and use it. Thanks a lot. Regards |
I tried and it works,thanks xiaozhu36 |
Hi alicloud_instance.instance0: Creating... Error: Error applying plan: 1 error(s) occurred:
|
@BlaCatRu I am sorry for that. At present, result from some inner reason, we can not support international account(your account is international account) to create 'PrePaid' instance. But we are working on resolving it and please be patient, thanks a lot. Regards |
Improve fc test case using new datasource alicloud_account
时过境迁,过了N年 ,问题依旧. |
@ningblue 你好,现在已经支持创建预付费的 ECS 实例了,可以提供下你的报错信息么? |
I try to use PrePaid, but api return not exist.
alicloud_instance.dev_api01: Creating...
allocate_public_ip: "" => "false"
availability_zone: "" => "cn-beijing-c"
host_name: "" => ""
image_id: "" => "ubuntu_16_0402_64_20G_alibase_20170818.vhd"
instance_charge_type: "" => "PrePaid"
instance_name: "" => "bj_dev_api01"
instance_type: "" => "ecs.mn4.xlarge"
internet_charge_type: "" => ""
is_outdated: "" => "true"
key_name: "" => ""
password: "" => ""
period: "" => "1"
private_ip: "" => ""
public_ip: "" => ""
security_groups.#: "" => "1"
security_groups.2177678232: "" => "sg-2ze0wnkgoh2tr4gj8b9u"
status: "" => ""
subnet_id: "" => ""
system_disk_category: "" => "cloud_efficiency"
system_disk_size: "" => ""
tags.%: "" => "1"
tags.Name: "" => "bj-dev-api01"
user_data: "" => "#!/bin/bash -v\napt-get update -y\n#apt-get dist-upgrade -y\napt-get install docker-compose -y\n"
vswitch_id: "" => "vsw-2ze467p48427f6mjipcpq"
Error: Error applying plan:
1 error(s) occurred:
alicloud_instance.dev_api01: 1 error(s) occurred:
alicloud_instance.dev_api01: Error creating Aliyun ecs instance: &common.Error{ErrorResponse:common.ErrorResponse{Response:common.Response{RequestId:"00072C24-46F2-4164-A997-2DC0F9F0F2F6"}, HostId:"ecs-cn-hangzhou.aliyuncs.com", Code:"InvalidInstanceChargeType.NotFound", Message:"The InstanceChargeType does not exist in our records"}, StatusCode:404}
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
The text was updated successfully, but these errors were encountered: