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

Azure automation_account connection and certificate objects #3881

Closed
ghost opened this issue Jul 19, 2019 · 4 comments · Fixed by #6847
Closed

Azure automation_account connection and certificate objects #3881

ghost opened this issue Jul 19, 2019 · 4 comments · Fixed by #6847

Comments

@ghost
Copy link

ghost commented Jul 19, 2019

This issue was originally opened by @bikashkarmakar as hashicorp/terraform#22141. It was migrated here as a result of the provider split. The original body of the issue is below.


Hi
We use automation account with a service principal (created with certifiacte -> az ad sp create-for-rbac --name ServicePrincipalName01 --create-cert ). We need to associate the automation account connection (of type AzureServicePrincipal) and certificate (the Service Principal certificate).

As per https://www.terraform.io/docs/providers/azurerm/r/automation_account.html , there is no object for connection and certificate. Can you please advise if this is supported ?

@MMollyy
Copy link

MMollyy commented Sep 25, 2019

Any comments on this?
Personally I'm actually more curious on the block properties, or seperate resources on defining/using the Run as accounts. Which I assume would go into the same structure as the service principal that could be provided?

Also, handling custom roles + scope to such service principals should be included.

I would also like to note this:
#4431

Seems like these two issues would go very well together.

@azdevad1
Copy link

I am at the same crossroads. Not able to create an azure run as account for automation using Terraform. I am reading issues and fixes related to this but not sure what is a good alternative to get this implemented until such a seamless association is provided. I have heard in bits and pieces on the work around to do this but don't have a direction. Can you kindly help me on how to achieve this as a contingency ?

@tombuildsstuff tombuildsstuff modified the milestones: v2.16.0, v2.17.0, v2.18.0 Jun 25, 2020
katbyte pushed a commit that referenced this issue Jul 8, 2020
…ection_certificate`,`azurerm_automation_connection_classic_certificate`and`azurerm_automation_connection_service_pricipal` (#6847)

(fixes #3881)
@ghost
Copy link
Author

ghost commented Jul 10, 2020

This has been released in version 2.18.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.18.0"
}
# ... other configuration ...

@ghost
Copy link
Author

ghost commented Aug 7, 2020

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Aug 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.