feat: iam policy ressource add conditions and expire at #1170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces support for conditions in IAM policies. Conditions allow to restrict permissions based on resources, date or customer's information.
It also adds an
expired_atattribute to policies.The
conditionsattribute is implemented with a 3-level nested schema. This is a workaround for the fact that Terraform does not support recursive schema definitions. The depth of 3 levels was chosen as a reasonable default, but this can be adjusted in the future if needed.This PR also includes two minor bug fixes:
ovh_cloud_project_network_privateresource. This was a minor fix to remove an unnecessaryfmt.Sprintf.fmt.Errorfcall.Type of change
How Has This Been Tested?
The new
conditionsandexpired_atattributes have been tested with acceptance tests.make testacc TESTARGS="-run TestAccIamPolicy_conditions"make testacc TESTARGS="-run TestAccIamPolicy_withExpirationDate"make testacc TESTARGS="-run TestAccIamPolicy"Test Configuration:
terraform version: Terraform v1.11.3Checklist:
go mod vendorif I added or modifygo.modfile