-
Hello!
When I try do modify `product_name` of megaport_mve resource I receive provider error:
error message appear during apply phase:
```
Terraform used the selected providers to generate the…
-
While upgrading from v0.4.1 to the latest v1.1.1 I had to remove VXC resources due to backwards incompatible changes only to realize that importing and updating resources does not work afterwards. I'm…
-
Something changed on Azure side and destroy for VXC doesn't work anymore and requires to remove peering connection from express route first, probably need some adjustment for VXC deletion process on M…
-
**Describe the bug**
```
$ terraform --version
Terraform v1.9.5
on linux_amd64
$ terraform init -upgrade
Initializing the backend...
Initializing provider plugins...
- Finding megaport/megapor…
-
**Describe the bug**
- When trying to create a new MVE using `Palo Alto VM-Series - Version 10.2.9-h1`, I receive a validation error:
```txt
Error: Validation error while attempting to create MVE…
-
**Describe the bug**
Errors in Documentation
**Terraform and Provider Version**
Megaport Provider version: 1.1.1
**Additional context**
Nested schema names are wrong.
- Nested Schema for a…
-
Hello!
`cost_centre` value fails to apply to `megaport_vxc` with following error:
```
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to megaport_vxc.…
-
Hello!
While modifying VXC config via Terraform I have encountered unexpected behavior and error. My goal was to change AWS VXC a_end config (untagged -> vlan). Terraform plan looked suspicious - i…
-
`accept_purchase_terms=false` is not accepted by the provider.
Code:
```
# Initialize the Megaport provider using credentials from AWS Secret Manager
provider "megaport" {
access_key …
-
Provider produced inconsistent result after apply for megaport_vxc resource.
Code
```hcl
resource "megaport_vxc" "aws" {
product_name = "${var.name_prefix}-AWS-VXC"
rate_limit …