Styjun

Applications of mathematics in clinical setting

What do you call the battery slot's ends?

What's the word for a student who doesn't register but goes to a class anyway?

removing rows containing NA in every column

Does rpcpassword need to be non-obvious in bitcoind?

Why can't we use uninitialized local variable to access static content of its type?

All numbers in a 5x5 Minesweeper grid

Account creation and log-in system

Madrid to London w/ Expired 90/180 days stay as US citizen

Plot irregular circle in latex

Can a business put a specific cancel-by date into a contract?

How often is duct tape used during crewed space missions?

What to do as a player when ranger animal companion dies

Abilities interrupting effects on a cast card

How could artificial intelligence harm us?

How to convey to the people around me that I want to disengage myself from constant giving?

Should the pagination be reset when changing the order?

How do rulers get rich from war?

Is a global DNS record a security risk for phpMyAdmin?

What are the end bytes of *.docx file format

Which block cipher parameters should be kept secret?

If people's daily habits are reliable then why is the stock market so unpredictable?

Exam design: give maximum score per question or not?

Can a Druid Wild Shaped as a horse use Horseshoes of Speed?

terraform apply fails while creating a resource that exists already

Migrating existing infrastructure & scaling with Terraformterraform import using name tag for the resourceTerraform: will dependent resource get created if parent partially completes with error?Use IAM role instead of credentials to create aws resource from an EC2 instance using terraformupdate existing infrastructure on heroku using terraformHow do I create an SSH key in terraform?Terraform forget resource and recreate?Terraform apply after Terraform import wants to force new resource for storage gateway cacheHow to refer to alternate resources in Terraform?Terraform resource recreation dynamic AWS RDS instance counts

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

I am working on terraform with openstack as the cloud provider. I have a deploy.tf script that creates a role:

resource "openstack_identity_role_v3" "role_example" 
 name = "creator"

My finding on how terraform creates resources:

• If the role does not exist in openstack, terraform creates one with
  no problem.


• If the role exists in openstack and is created with the
  same terraform script, ie. terraform.state has an entry of it,
  terraform returns with no errors.

my issue is: if I remove the state file or if the role is created out of bands either manually or by some other terraform script.I get the following error:

* openstack_identity_role_v3.role_example: Error creating OpenStack role: Expected HTTP response code [201] when accessing [POST https://<example-openstack-url>/v3/roles], but got 409 instead
"error": "message": "Conflict occurred attempting to store role - Duplicate Entry", "code": 409, "title": "Conflict"

I am trying to find a workaround so that if the role doesn't exist, terraform apply creates it, and if it already exists, despite having created manually or by any other terraform deployment script, terraform skips its creation and throw no error.

terraform openstack openstack-keystone terraform-provider-openstack

share|improve this question

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Run terraform import
  
  – victor m
  Mar 28 at 14:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Import certainly helps with manual creation, but managing it in another TF module or removing the state file are both circumstances that should not occurr.
  
  – Matt Schuchard
  Mar 28 at 15:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thanks for the suggestion. What I can see is that "terraform import" requires two arguments; "address" and "ID". I wish to achive the same without providing ID. because, if the role doesn't exist, I cannot know the value for Id.
  
  – Vedant Aggrawal
  Mar 28 at 15:37
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The ID is the resource in your config.
  
  – Matt Schuchard
  Mar 28 at 15:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  "terraform import openstack_identity_role_v3.role_example <ID>" is the correct syntax. Please help me substitute the value for ID. This works if I provide a hardcoded hash ID, but I want to provide it programmatically. thanks
  
  – Vedant Aggrawal
  Mar 28 at 15:52
  

  
  
  
  

 | 
show 3 more comments

0

I am working on terraform with openstack as the cloud provider. I have a deploy.tf script that creates a role:

resource "openstack_identity_role_v3" "role_example" 
 name = "creator"

My finding on how terraform creates resources:

• If the role does not exist in openstack, terraform creates one with
  no problem.


• If the role exists in openstack and is created with the
  same terraform script, ie. terraform.state has an entry of it,
  terraform returns with no errors.

my issue is: if I remove the state file or if the role is created out of bands either manually or by some other terraform script.I get the following error:

* openstack_identity_role_v3.role_example: Error creating OpenStack role: Expected HTTP response code [201] when accessing [POST https://<example-openstack-url>/v3/roles], but got 409 instead
"error": "message": "Conflict occurred attempting to store role - Duplicate Entry", "code": 409, "title": "Conflict"

I am trying to find a workaround so that if the role doesn't exist, terraform apply creates it, and if it already exists, despite having created manually or by any other terraform deployment script, terraform skips its creation and throw no error.

terraform openstack openstack-keystone terraform-provider-openstack

share|improve this question

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Run terraform import
  
  – victor m
  Mar 28 at 14:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Import certainly helps with manual creation, but managing it in another TF module or removing the state file are both circumstances that should not occurr.
  
  – Matt Schuchard
  Mar 28 at 15:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thanks for the suggestion. What I can see is that "terraform import" requires two arguments; "address" and "ID". I wish to achive the same without providing ID. because, if the role doesn't exist, I cannot know the value for Id.
  
  – Vedant Aggrawal
  Mar 28 at 15:37
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The ID is the resource in your config.
  
  – Matt Schuchard
  Mar 28 at 15:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  "terraform import openstack_identity_role_v3.role_example <ID>" is the correct syntax. Please help me substitute the value for ID. This works if I provide a hardcoded hash ID, but I want to provide it programmatically. thanks
  
  – Vedant Aggrawal
  Mar 28 at 15:52
  

  
  
  
  

 | 
show 3 more comments

I am working on terraform with openstack as the cloud provider. I have a deploy.tf script that creates a role:

resource "openstack_identity_role_v3" "role_example" 
 name = "creator"

My finding on how terraform creates resources:

• If the role does not exist in openstack, terraform creates one with
  no problem.


• If the role exists in openstack and is created with the
  same terraform script, ie. terraform.state has an entry of it,
  terraform returns with no errors.

my issue is: if I remove the state file or if the role is created out of bands either manually or by some other terraform script.I get the following error:

* openstack_identity_role_v3.role_example: Error creating OpenStack role: Expected HTTP response code [201] when accessing [POST https://<example-openstack-url>/v3/roles], but got 409 instead
"error": "message": "Conflict occurred attempting to store role - Duplicate Entry", "code": 409, "title": "Conflict"

I am trying to find a workaround so that if the role doesn't exist, terraform apply creates it, and if it already exists, despite having created manually or by any other terraform deployment script, terraform skips its creation and throw no error.

terraform openstack openstack-keystone terraform-provider-openstack

share|improve this question

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges

resource "openstack_identity_role_v3" "role_example" 
 name = "creator"

* openstack_identity_role_v3.role_example: Error creating OpenStack role: Expected HTTP response code [201] when accessing [POST https://<example-openstack-url>/v3/roles], but got 409 instead
"error": "message": "Conflict occurred attempting to store role - Duplicate Entry", "code": 409, "title": "Conflict"

share|improve this question

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges

share|improve this question

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges

asked Mar 28 at 13:54

Vedant AggrawalVedant Aggrawal

14522 silver badges1414 bronze badges