405 Error when spinning up Terraform Prismacloud producer

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

405 Error when spinning up Terraform Prismacloud producer

L1 Bithead

 

We're getting a 405 Error "405 not allowed" when running "terraform apply" to invoke a Terraform prismacloud producer.  Anyone seen this?  This is most likely a simple Terraform syntax error.

Thanks.

 

Notes:

1) "terraform init", "fmt", and "validate" all return without error

2) vpn disabled, but still no success

3) main.tf references a separate Prisma authentication json file

 

    main.tf:

    provider "prismacloud" {
        json_config_file = ".prismacloud_auth.json"
    }

 

    .prismacloud_auth.json file

    {

        "url": "app3.prismacloud.io",
        "username": "xxxx-user-id",
        "password": "yyyy-user-secret",
        "protocol": "https"

    }

 

4) This curl command returns valid html from Prisma, with no error

curl -u xxxx-user-id:yyyy-user-secret https://app3.prismacloud.io

 

5) terraform.log snippet in TRACE mode shows:

2022-06-23T16:14:53.869Z [DEBUG] checking for provisioner in "."
2022-06-23T16:14:53.872Z [DEBUG] checking for provisioner in "/usr/bin"
2022-06-23T16:14:53.872Z [TRACE] Meta.Backend: backend <nil> does not support operations, so wrapping it in a local backend
2022-06-23T16:14:53.872Z [TRACE] backend/local: state manager for workspace "default" will:
- read initial snapshot from terraform.tfstate
- write new snapshots to terraform.tfstate
- create any backup at terraform.tfstate.backup
2022-06-23T16:14:53.872Z [TRACE] statemgr.Filesystem: reading initial snapshot from terraform.tfstate
2022-06-23T16:14:53.873Z [TRACE] statemgr.Filesystem: read snapshot with lineage "29bd2382-e9b4-60f0-c2f0-cb5a1f023fd6" serial 1
2022-06-23T16:14:53.874Z [DEBUG] Service discovery for registry.terraform.io at https://registry.terraform.io/.well-known/terraform.json
2022-06-23T16:14:53.874Z [TRACE] HTTP client GET request to https://registry.terraform.io/.well-known/terraform.json
2022-06-23T16:14:53.906Z [DEBUG] GET https://registry.terraform.io/v1/providers/paloaltonetworks/prismacloud/versions
2022-06-23T16:14:53.906Z [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/paloaltonetworks/prismacloud/versions
2022-06-23T16:14:53.918Z [TRACE] providercache.fillMetaCache: scanning directory .terraform/providers
2022-06-23T16:14:53.918Z [TRACE] getproviders.SearchLocalDirectory: found registry.terraform.io/paloaltonetworks/prismacloud v1.2.6 for linux_amd64 at .terraform/providers/registry.terraform.io/paloaltonetworks/prismacloud/1.2.6/linux_amd64
@@@

 

fmi-blogger
1 ACCEPTED SOLUTION

Accepted Solutions

Thanks so much for the quick response.  I'll do that.

fmi-blogger

View solution in original post

2 REPLIES 2

Cyber Elite
Cyber Elite

This is the section for Prisma Access the Firewall as a Service solution not the Prisma Cloud. Better post this under the correct section.

Thanks so much for the quick response.  I'll do that.

fmi-blogger
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!