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

azuread_application: support the features block and the tags property #630

Merged
merged 6 commits into from
Oct 15, 2021

Conversation

manicminer
Copy link
Contributor

Closes: #327

@manicminer
Copy link
Contributor Author

Test results

Screenshot 2021-10-12 at 21 49 00

Screenshot 2021-10-12 at 21 50 14

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @manicminer - overall looks good and i have some questions of schema

docs/data-sources/application.md Outdated Show resolved Hide resolved
docs/data-sources/application.md Outdated Show resolved Hide resolved
@@ -214,6 +215,40 @@ func applicationDataSource() *schema.Resource {
Computed: true,
},

"features": {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we be explicit and call this

Suggested change
"features": {
"tags_features": {

or

Suggested change
"features": {
"tag_enabled_features": {

@@ -162,6 +167,7 @@ The following arguments are supported:
* `device_only_auth_enabled` - (Optional) Specifies whether this application supports device authentication without a user. Defaults to `false`.
* `display_name` - (Required) The display name for the application.
* `fallback_public_client_enabled` - (Optional) Specifies whether the application is a public client. Appropriate for apps using token grant flows that don't use a redirect URI. Defaults to `false`.
* `features` - (Optional) A `features` block as described below. Cannot be used together with the `tags` property. Features applied to this application will propagate to, and supplement any features/tags configured for, a linked service principal.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we be explicit that this is basically a shortcut to setting specific tags?

- Deprecate the `features` block for the `azuread_service_principal` resource / data source
- Make all features enabling (change `visible_to_users` to `hide`) so that tag values are always set by enabling a feature
@manicminer
Copy link
Contributor Author

Test results

Screenshot 2021-10-14 at 23 48 07

Screenshot 2021-10-14 at 23 48 14

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🏗️

@katbyte katbyte merged commit d128734 into main Oct 15, 2021
@katbyte katbyte deleted the features/application-features-tags branch October 15, 2021 01:22
katbyte added a commit that referenced this pull request Oct 15, 2021
@github-actions
Copy link

This functionality has been released in v2.7.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow Application Tags To Be Configured
2 participants