Add support to manage access packages in identitygovernance

docs/data-sources/access_package.md

@@ -0,0 +1,53 @@
+---
+subcategory: "Identity Governance"
+---
+
+# Data Source: azuread_access_package
+
+Use this data source to retrieve information for an existing access package within Identity Governance in Azure Active Directory.
+
+## API Permissions
+
+The following API permissions are required in order to use this data source.
+
+When authenticated with a service principal, this data source requires one of the following application roles: `EntitlementManagement.Read.All`, or `EntitlementManagement.ReadWrite.All`.
+
+When authenticated with a user principal, this data source requires one of the following directory roles: `Catalog owner`, `Catalog reader`, `Access package manager`, `Global Reader`, or `Global Administrator`.
+
+## Example Usage
+
+*Look up by ID*
+
+```terraform
+data "azuread_access_package" "example" {
+  object_id = "00000000-0000-0000-0000-000000000000"
+}
+```
+
+*Look up by DisplayName*
+
+```terraform
+data "azuread_access_package" "example" {
+  catalog_id   = "00000000-0000-0000-0000-000000000000"
+  display_name = "My access package Catalog"
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `catalog_id` - (Optional) The ID of the Catalog this access package is in.
+* `display_name` - (Optional) The display name of the access package.
+* `object_id` - (Optional) The ID of this access package.
+
+~> Either `object_id`, or both `catalog_id` and `display_name`, must be specified.
+
+
+## Attributes Reference
+
+In addition to the above arguments, the following attributes are exported:
+
+* `id` - The ID of this resource.
+* `description` - The description of the access package.
+* `hidden` - Whether the access package is hidden from the requestor.

docs/data-sources/access_package_catalog.md

@@ -0,0 +1,52 @@
+---
+subcategory: "Identity Governance"
+---
+
+# Data Source: azuread_access_package_catalog
+i
+Use this resource to retrieve information for an existing access package catalog within Identity Governance in Azure Active Directory.
+
+## API Permissions
+
+The following API permissions are required in order to use this data source.
+
+When authenticated with a service principal, this data source requires one of the following application roles: `EntitlementManagement.Read.All`, or `EntitlementManagement.ReadWrite.All`.
+
+When authenticated with a user principal, this data source requires one of the following directory roles: `Catalog owner`, `Catalog reader`, `Global Reader`, or `Global Administrator`.
+
+## Example Usage
+
+*Look up by ID*
+
+```terraform
+data "azuread_access_package_catalog" "example" {
+  object_id = "00000000-0000-0000-0000-000000000000"
+}
+```
+
+*Look up by DisplayName*
+
+```terraform
+data "azuread_access_package_catalog" "example" {
+  display_name = "My access package Catalog"
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `display_name` - (Optional) The display name of the access package catalog.
+* `object_id` - (Optional) The ID of this access package catalog.
+
+~> One of `display_name` or `object_id` must be specified.
+
+## Attributes Reference
+
+In additional to the arguments, the following attributes are exported:
+
+* `id` - The ID of this resource.
+* `description` - The description of the access package catalog.
+* `externally_visible` - Whether the access packages in this catalog can be requested by users outside the tenant.
+* `published` - Whether the access packages in this catalog are available for management.
+

docs/resources/access_package.md

@@ -0,0 +1,54 @@
+---
+subcategory: "Identity Governance"
+---
+
+# Resource: azuread_access_package
+
+Manages an Access Package within Identity Governance in Azure Active Directory.
+
+## API Permissions
+
+The following API permissions are required in order to use this resource.
+
+When authenticated with a service principal, this resource requires the following application role: `EntitlementManagement.ReadWrite.All`.
+
+When authenticated with a user principal, this resource requires one of the following directory roles: `Catalog owner`, `Access package manager` or `Global Administrator`
+
+
+## Example Usage
+
+```terraform
+resource "azuread_access_package_catalog" "example" {
+  display_name = "example-catalog"
+  description  = "Example catalog"
+}
+
+resource "azuread_access_package" "example" {
+  catalog_id   = azuread_access_package_catalog.example.id
+  display_name = "access-package"
+  description  = "Access Package"
+}
+```
+
+## Argument Reference
+
+* `catalog_id` - (Required) The ID of the Catalog this access package will be created in.
+* `description` - (Required) The description of the access package.
+* `display_name` - (Required) The display name of the access package.
+* `hidden` - (Optional) Whether the access package is hidden from the requestor.
+
+## Attributes Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+* `id` - The ID of this resource.
+
+## Import
+
+Access Packages can be imported using the `id`, e.g.
+
+```
+terraform import azuread_access_package.example_package 00000000-0000-0000-0000-000000000000
+```
+
+

docs/resources/access_package_assignment_policy.md

@@ -0,0 +1,210 @@
+---
+subcategory: "Identity Governance"
+---
+
+# Resource: azuread_access_package_assignment_policy
+
+Manages an assignment policy for an access package within Identity Governance in Azure Active Directory.
+
+## API Permissions
+
+The following API permissions are required in order to use this resource.
+
+When authenticated with a service principal, this resource requires the following application role: `EntitlementManagement.ReadWrite.All`.
+
+When authenticated with a user principal, this resource requires `Global Administrator` directory role, or one of the `Catalog Owner` and `Access Package Manager` role in Idneity Governance.
+
+## Example Usage
+
+```terraform
+resource "azuread_group" "example" {
+  display_name     = "group-name"
+  security_enabled = true
+}
+
+resource "azuread_access_package_catalog" "example" {
+  display_name = "example-catalog"
+  description  = "Example catalog"
+}
+
+resource "azuread_access_package" "example" {
+  catalog_id   = azuread_access_package_catalog.example.id
+  display_name = "access-package"
+  description  = "Access Package"
+}
+
+resource "azuread_access_package_assignment_policy" "test" {
+  access_package_id = azuread_access_package.test.id
+  display_name      = "assignment-policy"
+  description       = "My assignment policy"
+  duration_in_days  = 90
+
+  requestor_settings {
+    scope_type = "AllExistingDirectoryMemberUsers"
+  }
+
+  approval_settings {
+    approval_required = true
+
+    approval_stage {
+      approval_timeout_in_days = 14
+
+      primary_approver {
+        object_id    = azuread_group.test.object_id
+        subject_type = "groupMembers"
+      }
+    }
+  }
+
+  assignment_review_settings {
+    enabled                        = true
+    review_frequency               = "weekly"
+    duration_in_days               = 3
+    review_type                    = "Self"
+    access_review_timeout_behavior = "keepAccess"
+  }
+
+  question {
+    text {
+      default_text = "hello, how are you?"
+    }
+  }
+}
+```
+
+
+## Argument Reference
+
+- `access_package_id` (Required) The ID of the access package that will contain the policy.
+- `description` (Required) The description of the policy.
+- `display_name` (Required) The display name of the policy.
+- `approval_settings` (Optional) An `approval_settings` block to specify whether approvals are required and how they are obtained, as documented below.
+- `assignment_review_settings` (Optional) An `assignment_review_settings` block, to specify whether assignment review is needed and how it is conducted, as documented below.
+- `can_extend` (Optional) When enabled, users will be able to request extension of their access to this package before their access expires.
+- `duration_in_days` (Optional) How many days this assignment is valid for.
+- `expiration_date` (Optional) The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).
+- `question` (Optional) One or more `question` blocks for the requestor, as documented below.
+- `requestor_settings` (Optional) A `requestor_settings` block to configure the users who can request access, as documented below.
+
+---
+
+`approval_settings` block supports the following:
+
+- `approval_stage` (Optional) An `approval_stage` block specifying the process to obtain an approval, as documented below.
+- `approval_required` (Optional) Whether an approval is required.
+- `approval_required_for_extension` (Optional) Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.
+- `requestor_justification_required` (Optional) Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.
+
+---
+
+`approval_settings.approval_stage` block supports the following
+
+- `approval_timeout_in_days` (Required) Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.
+- `alternative_approver` (Optional) A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.
+- `enable_alternative_approval_in_days` (Optional) Number of days before the request is forwarded to alternative approvers.
+- `alternative_approval_enabled` (Optional) Whether alternative approvers are enabled.
+- `approver_justification_required` (Optional) Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.
+- `primary_approver` (Optional) A block specifying the users who will be asked to approve requests, as documented below.
+
+---
+
+`approval_settings.approval_stage.primary_approver` and `approval_settings.approval_stage.alternative_approver` blocks support the following:
+
+- `subject_type` (Required) Specifies the type of users. Valid values are `singleUser`, `groupMembers`, `connectedOrganizationMembers`, `requestorManager`, `internalSponsors`, or `externalSponsors`.
+- `backup` (Optional) For a user in an approval stage, this property indicates whether the user is a backup fallback approver.
+- `object_id` (Optional) The ID of the subject.
+
+---
+
+`assignment_review_settings` block supports the following:
+
+- `access_review_timeout_behavior` (Optional) Specifies the actions the system takes if reviewers don't respond in time. Vlid values are `keepAccess`, `removeAccess`, or `acceptAccessRecommendation`.
+- `duration_in_days` (Number) How many days each occurrence of the access review series will run.
+- `access_recommendation_enabled` (Optional) Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.
+- `approver_justification_required` (Optional) Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.
+- `enabled` (Optional) Whether to enable assignment review.
+- `review_frequency` (Optional) This will determine how often the access review campaign runs, valid values are `weekly`, `monthly`, `quarterly`, `halfyearly`, or `annual`.
+- `review_type` (Optional) Self review or specific reviewers, valid values are `Self`, `Reviewers`.
+- `reviewer` (Optional) One or more `reviewer` blocks to specify the users who will be reviewers (when `review_type` is `Reviewers`), as documented below.
+- `starting_on` (Optional) This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date
+
+---
+
+`assignment_review_settings.reviewer` block supports the following:
+
+- `subject_type` (Required) Specifies the type of users. Valid values are `singleUser`, `groupMembers`, `connectedOrganizationMembers`, `requestorManager`, `internalSponsors`, or `externalSponsors`.
+- `backup` (Optional) For a user in an approval stage, this property indicates whether the user is a backup approver.
+- `object_id` (Optional) The ID of the subject.
+
+---
+
+`question` block supports the following:
+
+- `text` (Required) A block describing the content of this question, as documented below.
+- `choice` (Optional) One or more blocks configuring a choice to the question, as documented below.
+- `required` (Optional) Whether this question is required.
+- `sequence` (Optional) The sequence number of this question.
+
+---
+
+`question.text` block supports the following:
+
+- `default_text` (Required) The default text of this question.
+- `localized_text` (Optional) One or more blocks describing localized text of this question, as documented below.
+
+---
+
+`question.text.localized_text` block supports the following:
+
+- `content` (Required) The localized content of this question.
+- `language_code` (Required) The ISO 639 language code for this question content.
+
+---
+
+`question.choice` block supports the following:
+
+- `actual_value` (Required) The actual value of this choice.
+- `display_value` (Required) A block describing the display text of this choice, as documented below.
+
+---
+
+`question.choice.display_value` block supports the following:
+
+- `default_text` (Required) The default text of this question choice.
+- `localized_text` (Optional) One or more blocks describing localized text of this question choice, as documented below.
+
+---
+
+`question.choice.display_value.localized_text` block supports the following:
+
+- `content` (Required) The localized content of this question choice.
+- `language_code` (Required) The ISO 639 language code for this question choice content.
+
+---
+
+`requestor_settings` block supports the following:
+
+- `requests_accepted` (Optional) Whether to accept requests using this policy. When `false`, no new requests can be made using this policy.
+- `requestor` (Optional) A block specifying the users who are allowed to request on this policy, as documented below.
+- `scope_type` (Optional) Specifies the scopes of the requestors. Valid values are `AllConfiguredConnectedOrganizationSubjects`, `AllExistingConnectedOrganizationSubjects`, `AllExistingDirectoryMemberUsers`, `AllExistingDirectorySubjects`, `AllExternalSubjects`, `NoSubjects`, `SpecificConnectedOrganizationSubjects`, or `SpecificDirectorySubjects`.
+
+---
+
+`requestor_settings.requestor` block supports the following:
+
+- `subject_type` (Required) Specifies the type of users. Valid values are `singleUser`, `groupMembers`, `connectedOrganizationMembers`, `requestorManager`, `internalSponsors`, or `externalSponsors`.
+- `object_id` (Optional) The ID of the subject.
+
+## Attributes Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+- `id` (String) The ID of this resource.
+
+## Import
+
+An access package assignment policy can be imported using the ID, e.g.
+
+```shell
+terraform import azuread_access_package_assignment_policy.example 00000000-0000-0000-0000-000000000000
+```