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

chore: sync master #1

Closed
29 changes: 29 additions & 0 deletions .github/workflows/prow.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
name: "Prow github actions"
on:
issue_comment:
types: [created]

jobs:
execute:
runs-on: ubuntu-latest
steps:
- uses: chnsz/[email protected]
with:
prow-commands: |
/assign
/unassign
/approve
/retitle
/area
/kind
/priority
/remove
/lgtm
/close
/reopen
/lock
/milestone
/hold
/cc
/uncc
github-token: "${{ secrets.GITHUB_TOKEN }}"
27 changes: 27 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,32 @@
# CHANGELOG

## 1.44.0 (December 1, 2023)

FEATURES:

* **New Resource:**
- `flexibleengine_obs_bucket_object_acl` [GH-1052]
- `flexibleengine_obs_bucket_policy` [GH-1052]
- `flexibleengine_rds_backup` [GH-1058]
- `flexibleengine_rds_cross_region_backup_strategy` [GH-1058]
- `flexibleengine_rds_sql_audit` [GH-1058]

* **New Data Source:**
- `flexibleengine_account` [GH-1044]
- `flexibleengine_dms_kafka_flavors` [GH-1048]
- `flexibleengine_identity_projects` [GH-1044]
- `flexibleengine_rds_instances` [GH-1058]
- `flexibleengine_rds_engine_versions` [GH-1058]
- `flexibleengine_rds_backups` [GH-1058]
- `flexibleengine_vpcs` [GH-1057]
- `flexibleengine_vpc_subnets` [GH-1057]
- `flexibleengine_obs_buckets` [GH-1052]
- `flexibleengine_obs_bucket_object` [GH-1052]

BUG FIXES:

* `resource/flexibleengine_lb_pool_v3`: Fix the issue of creation failure [GH-1066]

## 1.43.0 (November 3, 2023)

FEATURES:
Expand Down
11 changes: 11 additions & 0 deletions OWNERS
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# List of usernames who may use /lgtm
reviewers:
- chengxiangdong
- niuzhenguo
- shichangkuo

# List of usernames who may use /approve
approvers:
- chengxiangdong
- niuzhenguo
- shichangkuo
4 changes: 1 addition & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,10 @@ Terraform FlexibleEngine Provider

<!-- markdownlint-disable-next-line MD034 -->
- Website: https://www.terraform.io
- [![Documentation](https://img.shields.io/badge/documentation-blue)](https://registry.terraform.io/providers/FlexibleEngineCloud/flexibleengine/latest/docs)
- [![Gitter chat](https://badges.gitter.im/hashicorp-terraform/Lobby.png)](https://gitter.im/hashicorp-terraform/Lobby)
- Mailing list: [Google Groups](http://groups.google.com/group/terraform-tool)

<!-- markdownlint-disable-next-line MD033 -->
<img src="https://cdn.rawgit.com/hashicorp/terraform-website/master/content/source/assets/images/logo-hashicorp.svg" width="600px">

Quick Start
-----------

Expand Down
73 changes: 73 additions & 0 deletions docs/data-sources/dcs_flavors.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
subcategory: "Distributed Cache Service (DCS)"
---

# flexibleengine_dcs_flavors

Use this data source to get a list of available DCS flavors.

## Example Usage

```hcl
data "flexibleengine_dcs_flavors" "flavors" {
capacity = "4"
}
```

## Argument Reference

The following arguments are supported:

* `region` - (Optional, String) Specifies the region in which to obtain the DCS flavors.
If omitted, the provider-level region will be used.

* `capacity` - (Required, Float) The total memory of the cache, in GB.
+ **Redis4.0, Redis5.0 and Redis6.0**: Stand-alone and active/standby type instance values:
`0.125`, `0.25`, `0.5`, `1`, `2`, `4`, `8`, `16`, `32` and `64`.
Cluster instance specifications support `4`,`8`,`16`,`24`, `32`, `48`, `64`, `96`, `128`, `192`,
`256`, `384`, `512`, `768` and `1024`.
+ **Redis3.0**: Stand-alone and active/standby type instance values: `2`, `4`, `8`, `16`, `32` and `64`.
Proxy cluster instance specifications support `64`, `128`, `256`, `512`, and `1024`.
+ **Memcached**: Stand-alone and active/standby type instance values: `2`, `4`, `8`, `16`, `32` and `64`.

* `engine` - (Optional, String) The engine of the cache instance. Valid values are *Redis* and *Memcached*.
Default value is *Redis*.

* `engine_version` - (Optional, String) The version of a cache engine.
It is mandatory when the engine is *Redis*, the value can be `3.0`, `4.0`, `5.0`, or `6.0`.

* `cache_mode` - (Optional, String) The mode of a cache engine. The valid values are as follows:
+ `single` - Single-node.
+ `ha` - Master/Standby.
+ `cluster` - Redis Cluster.
+ `proxy` - Proxy Cluster. Redis6.0 not support this mode.
+ `ha_rw_split` - Read/Write splitting. Redis6.0 not support this mode.

* `name` - (Optional, String) The flavor name of the cache instance.

* `cpu_architecture` - (Optional, String) The CPU architecture of cache instance.
Valid values *x86_64* and *aarch64*.

## Attribute Reference

In addition to all arguments above, the following attributes are exported:

* `flavors` - A list of DCS flavors.

The `flavors` block supports:

* `name` - The flavor name of the cache instance.

* `cache_mode` - The mode of a cache instance.

* `engine` - The engine of the cache instance. Value is *redis* or *memcached*.

* `engine_versions` - Supported versions of the specification.

* `cpu_architecture` - The CPU architecture of cache instance. Value is *x86_64* or *aarch64*.

* `capacity` - The total memory of the cache, in GB.

* `available_zones` - An array of available zones where the cache specification can be used.

* `ip_count` - Number of IP addresses corresponding to the specifications.
96 changes: 96 additions & 0 deletions docs/data-sources/dcs_instances.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,96 @@
---
subcategory: "Distributed Cache Service (DCS)"
---

# flexibleengine_dcs_instances

Use this data source to get the list of DCS instances.

## Example Usage

```hcl
data "flexibleengine_dcs_instances" "test" {
name = "test_name"
status = "RUNNING"
}
```

## Argument Reference

The following arguments are supported:

* `region` - (Optional, String) Specifies the region in which to query the data source.
If omitted, the provider-level region will be used.

* `name` - (Optional, String) Specifies the name of an instance.

* `status` - (Optional, String) Specifies the cache instance status. The valid values are **RUNNING**, **ERROR**,
**RESTARTING**, **FROZEN**, **EXTENDING**, **RESTORING**, **FLUSHING**.

* `private_ip` - (Optional, String) Specifies the subnet Network ID.

* `capacity` - (Optional, Float) Specifies the cache capacity. Unit: GB.

## Attribute Reference

In addition to all arguments above, the following attributes are exported:

* `id` - The resource ID.

* `instances` - Indicates the list of DCS instances.
The [Instance](#DcsInstance_Instance) structure is documented below.

<a name="DcsInstance_Instance"></a>
The `Instance` block supports:

* `id` - Indicates the ID of the instance.

* `name` - Indicates the name of an instance.

* `engine` - Indicates a cache engine.

* `engine_version` - Indicates the version of a cache engine.

* `capacity` - Indicates the cache capacity. Unit: GB.

* `flavor` - Indicates the flavor of the cache instance.

* `availability_zones` - Specifies the code of the AZ where the cache node resides.

* `vpc_id` - Indicates the ID of VPC which the instance belongs to.

* `vpc_name` - Indicates the name of VPC which the instance belongs to.

* `subnet_id` - Indicates the ID of subnet which the instance belongs to.

* `subnet_name` - Indicates the name of subnet which the instance belongs to.

* `security_group_id` - Indicates the ID of the security group which the instance belongs to.

* `security_group_name` - Indicates the name of security group which the instance belongs to.

* `enterprise_project_id` - Indicates the enterprise project id of the dcs instance.

* `description` - Indicates the description of an instance.

* `private_ip` - Indicates the IP address of the DCS instance.

* `maintain_begin` - Indicates the time at which the maintenance time window starts.

* `maintain_end` - Indicates the time at which the maintenance time window ends.

* `port` - Indicates the port of the cache instance.

* `status` - Indicates the cache instance status.

* `used_memory` - Indicates the size of the used memory. Unit: MB.

* `max_memory` - Indicates the total memory size. Unit: MB.

* `domain_name` - Indicates the domain name of the instance.

* `access_user` - Indicates the username used for accessing a DCS Memcached instance.

* `order_id` - Indicates the ID of the order that created the instance.

* `tags` - Indicates The key/value pairs to associate with the DCS instance.
6 changes: 3 additions & 3 deletions docs/data-sources/networking_port.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ subcategory: "Virtual Private Cloud (VPC)"

# flexibleengine_networking_port

Use this data source to get the ID of an available Flexibleengine port.
Use this data source to get the ID of an available FlexibleEngine port.

## Example Usage

Expand Down Expand Up @@ -40,12 +40,12 @@ In addition to all arguments above, the following attributes are exported:

* `name` - The name of the port.

* `admin_state_up` - The administrative state of the port.

* `device_owner` - The device owner of the port.

* `device_id` - The ID of the device the port belongs to.

* `all_allowed_ips` - The collection of allowed IP addresses on the port.

* `all_fixed_ips` - The collection of Fixed IP addresses on the port.

* `all_security_group_ids` - The collection of security group IDs applied on the port.
18 changes: 12 additions & 6 deletions docs/data-sources/vpc_peering_connection_v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,18 +27,24 @@ resource "flexibleengine_vpc_route_v2" "vpc_route" {
The arguments of this data source act as filters for querying the available VPC peering connection.
The given filters must match exactly one VPC peering connection whose data will be exported as attributes.

* `id` (Optional) - The ID of the specific VPC Peering Connection to retrieve.
* `region` - (Optional, String) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
If omitted, the region argument of the provider is used.

* `status` (Optional) - The status of the specific VPC Peering Connection to retrieve.
* `id` (Optional, String) - The ID of the specific VPC Peering Connection to retrieve.

* `vpc_id` (Optional) - The ID of the requester VPC of the specific VPC Peering Connection to retrieve.
* `name` (Optional, String) - The name of the specific VPC Peering Connection to retrieve.

* `peer_vpc_id` (Optional) - The ID of the accepter/peer VPC of the specific VPC Peering Connection to retrieve.
* `status` (Optional, String) - The status of the specific VPC Peering Connection to retrieve.

* `peer_tenant_id` (Optional) - The Tenant ID of the accepter/peer VPC of the specific VPC Peering Connection to retrieve.
* `vpc_id` (Optional, String) - The ID of the requester VPC of the specific VPC Peering Connection to retrieve.

* `name` (Optional) - The name of the specific VPC Peering Connection to retrieve.
* `peer_vpc_id` (Optional, String) - The ID of the accepter/peer VPC of the specific VPC Peering Connection to retrieve.

* `peer_tenant_id` (Optional, String) - The Tenant ID of the accepter/peer VPC
of the specific VPC Peering Connection to retrieve.

## Attributes Reference

* `description` - The description of the VPC Peering Connection.

All of the argument attributes are exported as result attributes.
5 changes: 4 additions & 1 deletion docs/data-sources/vpc_route_ids_v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,10 @@ output "route_nexthop" {

## Argument Reference

* `vpc_id` (Required) - The VPC ID that you want to filter from.
* `region` - (Optional, String) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
If omitted, the region argument of the provider is used.

* `vpc_id` (Required, String) - The VPC ID that you want to filter from.

## Attributes Reference

Expand Down
13 changes: 8 additions & 5 deletions docs/data-sources/vpc_route_v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,18 @@ The arguments of this data source act as filters for querying the available
routes in the current tenant. The given filters must match exactly one
route whose data will be exported as attributes.

* `id` (Optional) - The id of the specific route to retrieve.
* `region` - (Optional, String) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
If omitted, the region argument of the provider is used.

* `vpc_id` (Optional) - The id of the VPC that the desired route belongs to.
* `id` (Optional, String) - The id of the specific route to retrieve.

* `destination` (Optional) - The route destination address (CIDR).
* `vpc_id` (Optional, String) - The id of the VPC that the desired route belongs to.

* `tenant_id` (Optional) - Only the administrator can specify the tenant ID of other tenants.
* `destination` (Optional, String) - The route destination address (CIDR).

* `type` (Optional) - Route type for filtering.
* `tenant_id` (Optional, String) - Only the administrator can specify the tenant ID of other tenants.

* `type` (Optional, String) - Route type for filtering.

## Attribute Reference

Expand Down
7 changes: 6 additions & 1 deletion docs/data-sources/vpc_subnet_ids_v1.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,15 @@ output "subnet_cidr_blocks" {

The following arguments are supported:

* `vpc_id` (Required) - Specifies the VPC ID used as the query filter.
* `region` - (Optional, String) The region in which to obtain the V1 VPC client. A VPC client is needed to retrieve VPCs.
If omitted, the region argument of the provider is used.

* `vpc_id` (Required, String) - Specifies the VPC ID used as the query filter.

## Attributes Reference

The following attributes are exported:

* `id` - Specifies a data source ID in UUID format.

* `ids` - A list of all the subnet ids found. This data source will fail if none are found.
Loading
Loading