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

export primary and secondary keys of azurerm_search_service #1873

Closed
DimitriTchapmi opened this issue Sep 5, 2018 · 3 comments
Closed

export primary and secondary keys of azurerm_search_service #1873

DimitriTchapmi opened this issue Sep 5, 2018 · 3 comments

Comments

@DimitriTchapmi
Copy link

DimitriTchapmi commented Sep 5, 2018

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

When you build an azurerm_search_service with terraform, it just export you the id attribute. It will be great if we could get primary and secondary key in addition. This will be so usefull in many cases, for example when you need to automate tasks with Rest API. I'm trying to output those keys and use them in ansible tasks.

New or Affected Resource(s)

  • azurerm_search_service

Potential Terraform Configuration

output "search_pri_key" {
value = "${azurerm_search_service.mysearch.primary_key}"
}
@tombuildsstuff
Copy link
Contributor

hi @DimitriTchapmi

Just to let you know that support for this shipped in v1.17 - you can upgrade to this by updating the version in the Provider block (as shown below) and then running terraform init -upgrade:

provider "azurerm" {
  version = "=1.17.0"
}

Thanks!

@DimitriTchapmi
Copy link
Author

Thanks a lot

@ghost
Copy link

ghost commented Mar 6, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants