Giter Site home page Giter Site logo

stackpath / terraform-provider-stackpath Goto Github PK

View Code? Open in Web Editor NEW
6.0 20.0 12.0 11.44 MB

Terraform provider for StackPath

Home Page: https://www.terraform.io/docs/providers/stackpath/

License: Mozilla Public License 2.0

Makefile 1.59% Go 97.86% Shell 0.09% HTML 0.46%
terraform-provider stackpath terraform

terraform-provider-stackpath's Introduction

Terraform logo

Terraform Provider for StackPath

The StackPath provider is a plugin for Terraform to interact with resources on the StackPath edge platform. It is publicly available on the Terraform registry. Please see the official documentation to get started.

IMPORTANT NOTE: From 2.0.0 onward, the provider is assumed to be the only application controlling an Edge Compute workload. Any fields/properties managed outside of Terraform will be overwritten if they are not fields the provider is aware of. Performing a refresh is suggested after upgrading.

Provider development

Requirements

  • Terraform 0.12+ (to run acceptance tests)
  • Go 1.16+ (to build the provider plugin)

Building the provider

Run the following command to build the provider:

$ make build

Generating the StackPath API client code

We need to install swagger cli tool to generate StackPath API client code (See: https://goswagger.io/install.html) Note: Current client code is generated using go-swagger version v0.27.0, so it is recommended that we use same version to avoid client code differences being introduced due to latest version of swagger unless we decide to bump up client code versioning.

Once swagger cli is installed, Run the following command to generate client code:

$ make generate

Installing the built provider for Terraform < 0.13

Run the following command to install the built provider:

$ make install

Once the plugin has been installed, run terraform init to have terraform discover the StackPath plugin.

Installing the built provider for Terraform >= 0.13

Make sure that your terraform config is setup to mirror local providers: Something like this should be in your ~/.terraformrc

provider_installation {
  filesystem_mirror {
    path    = "/Users/USERNAME/terraform-providers/"
    include = ["local/providers/*"]
  }
  direct {
    exclude = ["local/providers/*"]
  }
}

Run the following command to install the built provider:

$ make install-13

Once the plugin has been installed, run terraform init to have terraform discover the StackPath plugin.

Testing the provider

Run the following command to run the provider's unit tests:

$ make test

In order to run the full suite of acceptance tests, run make testacc. You must declare a valid StackPath stack ID or slug, API client ID, and API client secret in the STACKPATH_STACK_ID, STACKPATH_CLIENT_ID, and STACKPATH_CLIENT_SECRET environment variables:

Note: Acceptance tests create real resources, and often cost money to run.

$ STACKPATH_STACK_ID=my-stack-id STACKPATH_CLIENT_ID=my-client-id STACKPATH_CLIENT_SECRET=my-client-secret make testacc

terraform-provider-stackpath's People

Contributors

bgabler avatar bobcob7 avatar cgriggs01 avatar davebond avatar jasonmillerstackpath avatar jdewald avatar jdtx0 avatar klaude avatar maheshtambe avatar nkoturovic avatar pionoor avatar prhomhyse avatar scotwells avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

terraform-provider-stackpath's Issues

The user_data argument in virtual_machine resource is throwing permission denied

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

Terraform Version

Terraform v0.12.23
-provider.stackpath v1.2.1

Affected Resource(s)

stackpath compute virtual machine

  • stackpath_compute_workload

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,

variable "stackpath_stack_id" {}
variable "stackpath_client_id" {}
variable "stackpath_client_secret" {}

provider "stackpath" {
  stack_id      = var.stackpath_stack_id
  client_id     = var.stackpath_client_id
  client_secret = var.stackpath_client_secret
}

resource "stackpath_compute_workload" "angix" {
  name = "anginx"
  slug = "anginx"

  annotations = {
    # request an anycast IP
    "anycast.platform.stackpath.net" = "true"
  }

  network_interface {
    network = "default"
  }

virtual_machine {
    name = "terranginx"
    image = "stackpath-edge/ubuntu-1804-bionic:v201909061930"
    user_data = "file(data.conf)"
    resources {
      requests = {
        "cpu"    = "1"
        "memory" = "2Gi"
      }
    }
}

    target {
    name         = "us"
    min_replicas = 1
    max_replicas = 2
    scale_settings {
      metrics {
        metric = "cpu"
        # Scale up when CPU averages 50%.
        average_utilization = 50
      }
    }
    # Deploy these 1 to 2 instances in Dallas, TX, USA and Amsterdam, NL.
    deployment_scope = "cityCode"
    selector {
      key      = "cityCode"
      operator = "in"
      values   = [
        "DFW", "AMS"
      ]
    }
  }
}


# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

None

Panic Output

No panic output.
Terraform apply worked fine

Expected Behavior

The ideal behavior should be like that of the Edge VM Workload created in the StackPath Dashboard.
I use the same ssh keys and the same keys worked the GUI created Edge VM but not the Terraform CLI.

Actual Behavior

The below is my cloud-init file content:

#cloud-config
ssh_authorized_keys:
  - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDcthLR0qW6y1eWtlmgUE/DveL4XCaqK6PQlWzi445v6vgh7emU4R5DmAsz+plWooJL40dDLCwBt9kEcO/vYzKY9DdHnX8dveMTJNU/OJAaoB1fV6ePvTOdQ6F3SlF2uq77xYTOqBiWjqF+KMDeB+dQ+eGyhuI/z/aROFP6pdkRyEikO9YkVMPyomHKFob+ZKPI4t7TwUi7x1rZB1GsKgRoFkkYu7gvGak3jEWazsZEeRxCgHgAV7TDm05VAWCrnX/+RzsQ/1DecwSzsP06DGFWZYjxzthhGTvH/W5+KFyMvyA+tZV4i1XM+CIv/Ma/xahwqzQkIaKUwsldPPu00jRN user@desktop

For safety/security reasons, I use a sample ssh-key also mentioned here.

When I go to the created VM Workload and settings I see the below:
VM Workload settings

I try to connect via ssh, I get the below:
Permission denied

Steps to Reproduce

  1. Generate or use your existing ssh keys in the cloud-init file
  2. terraform apply
  3. Turn on Remote Management
  4. Try to ssh to any instance

Important Factoids

From the StackPath provider docs, I already encoded the file with Base64.

user_data - (Optional) Base64-encoded cloud-init user data.

Unable to update workload.

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

Terraform Version

Terraform v1.0.11

Affected Resource(s)

  • stackpath_compute_workload

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

resource "stackpath_compute_network_policy" "edge-server-network-policy" {
  name        = "Network Policy for edge-server-workload"
  slug        = "workload-edge-servers"
  priority    = 64999

  instance_selector {
    key      = "workload.platform.stackpath.net/workload-slug"
    operator = "in"
    values   = ["edge-server-workload"]
  }

  policy_types = ["INGRESS"]

  ingress {
    action      = "ALLOW"
    description = "Allow port 80 + 443 traffic from all IPs"
    protocol {
      tcp {
        destination_ports = [80, 443]
      }
    }
    from {
      ip_block {
        cidr = "0.0.0.0/0"
      }
    }
  }
}

resource "stackpath_compute_workload" "edge-server-workload" {
  name = "edge-server-workload"
  slug = "edge-server-workload"

  annotations = {
    "anycast.platform.stackpath.net" = "true"
  }

  network_interface {
    network = "default"
  }

  container {
    name = "edge-server"
    image = "nginx:latest"

    resources {
      requests = {
        "cpu"    = "1"
        "memory" = "2Gi"
      }
    }

    env {
      key   = "VARIABLE_NAME"
      value = "VALUE"
    }
  }

  target {
    name         = "lhr-only"
    min_replicas = 1
    max_replicas = 3
    scale_settings {
      metrics {
        metric = "cpu"
        average_utilization = 50
      }
    }
    deployment_scope = "cityCode"
    selector {
      key      = "cityCode"
      operator = "in"
      values   = [
        "LHR"
      ]
    }
  }
}

Debug Output

Panic Output

โ”‚ Error: failed to update compute workload: a 400 error was returned from StackPath: "Invalid workload specification: workload.spec.networkInterfaces: Forbidden: network interface cannot be modified". The following fields have errors: workload.spec.networkInterfaces: Forbidden: network interface cannot be modified (request ID 3c4.....14d)
โ”‚ 
โ”‚   with stackpath_compute_workload.edge-server-workload,
โ”‚   on main.tf line 50, in resource "stackpath_compute_workload" "edge-server-workload":
โ”‚   50: resource "stackpath_compute_workload" "edge-server-workload" {
โ”‚ 

Expected Behavior

It should be able to modify an existing workload.

Actual Behavior

It is unable to modify an existing workload because 'network interface cannot be modified'. Unfortunately network_interface is required.

Steps to Reproduce

  1. terraform apply
  2. This will create a workload
  3. Change max_replicas to any number > 3. Or change image to "nginx:1.20"
  4. terraform apply
  5. You should cause a panic as shown above.

Important Factoids

References

  • #0000

DNS Record and DNS Zone Resources

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

The StackPath Terraform provider doesn't include the dns_record and dns_zone resources. These resources are crucial for managing DNS records and zones within StackPath and would tie in nicely when combining the provider with other providers to automate the provisioning of DNS for resources created by other providers.

New Resource(s)

  • stackpath_dns_record
  • stackpath_dns_zone

Potential Terraform Configuration

resource "stackpath_dns_zone" "example_zone" {
  domain = "example.com"
  labels = {}
}

resource "stackpath_dns_record" "www_record" {
  for_each = {
    "www" = "x.x.x.x"
    "@"   = "x.x.x.x"
  }

  zone_id = stackpath_dns_zone.example_zone.id
  name    = each.key
  type    = "A"
  ttl     = 43200
  data    = each.value
}

Provide instance public IP

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

In the stackpath_compute_workload resource, it would be useful if the network settings of the deployed workload became available in the resulting entity. This would facilitate making use of the public IP to update a DNS record elsewhere in the terraform config.

New or Affected Resource(s)

  • stackpath_compute_workload

Potential Terraform Configuration

resource "stackpath_compute_workload" "Example" {
 ...
}

resource "google_dns_record_set" "frontend" {
  name = "example.server.record"
  type = "A"
  ttl  = 300

  managed_zone = "server.record"

  rrdatas = [stackpath_compute_workload.Example.network_interface[0].?]
}

stackpath_compute_network_policy fails to create resource

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

Terraform Version

Terraform v0.12.23

  • provider.stackpath v1.2.1

Affected Resource(s)

  • stackpath_compute_network_policy

Terraform Configuration Files

This configuration file is the exact one in StackPath provider docs

resource "stackpath_compute_network_policy" "web-server" {
  name        = "Allow HTTP traffic to web servers"
  slug        = "web-servers-allow-http"
  description = "A network policy that allows HTTP access to instances with the web server role"
  priority    = 20000

  instance_selector {
    key      = "role"
    operator = "in"
    values   = ["web-server"]
  }

  policy_types = ["INGRESS"]

  ingress {
    action      = "ALLOW"
    description = "Allow port 80 traffic from all IPs"
    protocol {
      tcp {
        destination_ports = [80]
      }
    }
    from {
      ip_block {
        cidr = "0.0.0.0/0"
      }
    }
  }
}

Debug Output

stackpath_compute_network_policy.web-server: Creating...

Error: failed to create network policy: invalid @type value: "type.googleapis.com/stackpath.rpc.RequestInfo"

  on main.tf line 11, in resource "stackpath_compute_network_policy" "web-server":
  11: resource "stackpath_compute_network_policy" "web-server" {

NOTE: It is line 11 after I add the credential variables above the resource.

Expected Behavior

The network policy should be created.

Actual Behavior

The network policy was not created.

I tried to create a network policy that will open needed ports, 80 for example.

Steps to Reproduce

terraform apply

Important Factoids

After a workload is created with Terraform, you have to add the network policy from the dashboard as a work-around.

This network policy created with Terraform will automate the process.

Stackpath Workload Import Causes Terraform Crash

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

Terraform Version

Terraform v0.13.1

  • provider registry.terraform.io/terraform-providers/stackpath v1.3.2

Affected Resource(s)

  • stackpath_compute_workload

Terraform Configuration Files

terraform {
  required_providers {
    stackpath = {
      source = "terraform-providers/stackpath"
    }
  }
  required_version = ">= 0.13"
}

variable "STACKID" {}
variable "CLIENTID" {}
variable "SECRET" {}

provider "stackpath" {
  stack_id      = var.STACKID
  client_id     = var.CLIENTID
  client_secret = var.SECRET
}

resource "stackpath_compute_workload" "workloadname" {
}

Debug Output

stackpath_compute_workload.workloadname: Importing from ID "0a61802e-1edf-4d4d-9d15-686e327433b9"...
stackpath_compute_workload.workloadname: Import prepared!
Prepared stackpath_compute_workload for import
stackpath_compute_workload.workloadname: Refreshing state... [id=0a61802e-1edf-4d4d-9d15-686e327433b9]

Error: rpc error: code = Unavailable desc = transport is closing

panic: runtime error: index out of range [0] with length 0
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2:
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: goroutine 15 [running]:
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath.flattenComputeMatchExpressionsOrdered(0xc000917618, 0x11, 0xc000462c40, 0xc0007b8e40, 0x1, 0x4, 0x11, 0xc0005a8000, 0xc000917668)
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath/structure_core.go:107 +0x5d4
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath.flattenComputeWorkloadTarget(0xc0008823a8, 0x8, 0xc00079be3e, 0x2, 0xc000462c40, 0xc0007b8da0, 0x8)
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath/structure_compute_workload.go:505 +0x3cd
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath.flattenComputeWorkloadTargets(0x1d122de, 0x6, 0xc000462c40, 0xc00060d020, 0xc0000e0b60, 0x0, 0x0)
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath/structure_compute_workload.go:489 +0x51c
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath.flattenComputeWorkload(0xc000462c40, 0xc000136ee0, 0x0, 0x0)
2020-09-10T12:24:28.793-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath/structure_compute_workload.go:346 +0x8c3
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath.resourceComputeWorkloadRead(0xc000462c40, 0x1bb27a0, 0xc0002e2800, 0xc000462c40, 0x0)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/terraform-providers/terraform-provider-stackpath/stackpath/resource_stackpath_compute_workload.go:431 +0x23f
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/hashicorp/terraform-plugin-sdk/helper/schema.(*Resource).RefreshWithoutUpgrade(0xc000090ab0, 0xc00047d090, 0x1bb27a0, 0xc0002e2800, 0xc000123848, 0x0, 0x0)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/hashicorp/[email protected]/helper/schema/resource.go:460 +0x119
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/hashicorp/terraform-plugin-sdk/internal/helper/plugin.(*GRPCProviderServer).ReadResource(0xc000181500, 0x1f88900, 0xc00034b860, 0xc00074a900, 0xc000181500, 0xc00034b860, 0xc000643b78)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/hashicorp/[email protected]/internal/helper/plugin/grpc_provider.go:525 +0x3d8
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/hashicorp/terraform-plugin-sdk/internal/tfplugin5._Provider_ReadResource_Handler(0x1cd1c00, 0xc000181500, 0x1f88900, 0xc00034b860, 0xc00074a8a0, 0x0, 0x1f88900, 0xc00034b860, 0xc0004b60f0, 0xed)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: github.com/hashicorp/[email protected]/internal/tfplugin5/tfplugin5.pb.go:3269 +0x217
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/grpc.(*Server).processUnaryRPC(0xc000782a80, 0x1f93380, 0xc000783e00, 0xc000230800, 0xc00008a6f0, 0x27565b0, 0x0, 0x0, 0x0)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/[email protected]/server.go:1024 +0x501
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/grpc.(*Server).handleStream(0xc000782a80, 0x1f93380, 0xc000783e00, 0xc000230800, 0x0)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/[email protected]/server.go:1313 +0xd3d
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc0000363c0, 0xc000782a80, 0x1f93380, 0xc000783e00, 0xc000230800)
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/[email protected]/server.go:722 +0xa1
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: created by google.golang.org/grpc.(*Server).serveStreams.func1
2020-09-10T12:24:28.794-0700 [DEBUG] plugin.terraform-provider-stackpath_v1.3.2: google.golang.org/[email protected]/server.go:720 +0xa1
2020-09-10T12:24:28.796-0700 [WARN] plugin.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2020/09/10 12:24:28 [ERROR] eval: *terraform.EvalRefresh, err: rpc error: code = Unavailable desc = transport is closing
2020/09/10 12:24:28 [ERROR] eval: *terraform.EvalSequence, err: rpc error: code = Unavailable desc = transport is closing
2020/09/10 12:24:28 [TRACE] [walkImport] Exiting eval tree: import stackpath_compute_workload.workloadname result
2020/09/10 12:24:28 [TRACE] vertex "import stackpath_compute_workload.workloadname result": visit complete
2020/09/10 12:24:28 [TRACE] vertex "stackpath_compute_workload.workloadname (import id "0a61802e-1edf-4d4d-9d15-686e327433b9")": dynamic subgraph encountered errors
2020/09/10 12:24:28 [TRACE] vertex "stackpath_compute_workload.workloadname (import id "0a61802e-1edf-4d4d-9d15-686e327433b9")": visit complete
2020-09-10T12:24:28.796-0700 [DEBUG] plugin: plugin process exited: path=.terraform/plugins/registry.terraform.io/terraform-providers/stackpath/1.3.2/darwin_amd64/terraform-provider-stackpath_v1.3.2 pid=20263 error="exit status 2"
2020/09/10 12:24:28 [TRACE] dag/walk: upstream of "provider["registry.terraform.io/terraform-providers/stackpath"] (close)" errored, so skipping
2020/09/10 12:24:28 [TRACE] dag/walk: upstream of "root" errored, so skipping
2020/09/10 12:24:28 [TRACE] statemgr.Filesystem: removing lock metadata file .terraform.tfstate.lock.info
2020/09/10 12:24:28 [TRACE] statemgr.Filesystem: unlocking terraform.tfstate using fcntl flock
2020-09-10T12:24:28.798-0700 [DEBUG] plugin: plugin exited

!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Terraform crashed! This is always indicative of a bug within Terraform.
A crash log has been placed at "crash.log" relative to your current
working directory. It would be immensely helpful if you could please
report the crash with Terraform1 so that we can fix this.

When reporting bugs, please include your terraform version. That
information is available on the first line of crash.log. You can also
get it by running 'terraform --version' on the command line.

SECURITY WARNING: the "crash.log" file that was created may contain
sensitive information that must be redacted before it is safe to share
on the issue tracker.

!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Panic Output

crash.log

Expected Behavior

Successful workload import

Actual Behavior

!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Terraform crashed! This is always indicative of a bug within Terraform.
A crash log has been placed at "crash.log" relative to your current
working directory. It would be immensely helpful if you could please
report the crash with Terraform1 so that we can fix this.

When reporting bugs, please include your terraform version. That
information is available on the first line of crash.log. You can also
get it by running 'terraform --version' on the command line.

SECURITY WARNING: the "crash.log" file that was created may contain
sensitive information that must be redacted before it is safe to share
on the issue tracker.

!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Steps to Reproduce

  1. tterraform import stackpath_compute_workload.workloadname xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Important Factoids

N/A

References

hashicorp/terraform#26088

  • #0000

Swagger / OpenAPI specification not available

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

Client and model code [0] is generated using go-swagger but there is no specification currently available, this leaves the project in a state where it cannot be developed in a way which would pass PR and be merged upstream. In our case we are trying to add support for stackpath object storage.

We have asked stackpath support for access to the specification but have been told that there is no public facing spec that they can share.

[0] https://github.com/terraform-providers/terraform-provider-stackpath/blob/master/stackpath/internal/client/create_network_policy_parameters.go

New or Affected Resource(s)

  • All new resources

References

  • Stackpath support request 524637

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.