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

Provide support for approle outside of resource_application as an independent resource #306

Closed
gtmtech opened this issue Aug 18, 2020 · 3 comments · Fixed by #298
Closed

Comments

@gtmtech
Copy link
Contributor

gtmtech commented Aug 18, 2020

Description

Currently it is only possible to create approles through an application (resource_application.go)

In our AD setup, an enterprise application is created for us by another team, and we can only create approles within it. We have no permission to be able to create or modify enterprise applications, but would like to be able to create and assign approles to users.

As with many terraform resources, it would be useful if both approaches were possible.

New or Affected Resource(s)

resource_application.go

@manicminer
Copy link
Member

Hi @gtmtech, thanks for requesting this! We have been considering additional standalone resources for applications, with the goal of making it possible to have more flexible configurations.

Until this is implemented, would you be able to work around this by importing the already existing application into your state? For example:

terraform import azuread_application.my_app 10000000-2000-3000-4000-500000000000

This will allow you to manage aspects of the application using Terraform, without needing to create it with Terraform in the first place.

@ghost
Copy link

ghost commented Sep 3, 2020

This has been released in version 1.0.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 "azuread" {
    version = "~> 1.0.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Oct 4, 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!

@hashicorp hashicorp locked as resolved and limited conversation to collaborators Oct 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants