-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
r/aws_datasync_agent: remove ExactlyOneOf activation_key, ip_address #35150
Conversation
This requirement previously prevented successful import of agents initialized with an activation_key. The `activation_key` is not returned by the read operation, so setting this required value in configuration always forced a new resource on the next apply. Practitioners could work around the issue with an `ignore_changes` `lifecycle` argument, but removing the `ExactlyOneOf` condition in favor of a `ConflictsWith` condition allows agents created with an activation key to be imported _without_ requiring the attribute to be set in the corresponding Terraform configuration.
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
This functionality has been released in v5.32.0 of the Terraform AWS 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! |
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 issues. |
Description
This requirement previously prevented successful import of agents initialized with an
activation_key
. Theactivation_key
is not returned by the read operation, so setting this required value in configuration always forced a new resource on the next apply. Practitioners could work around the issue with anignore_changes
lifecycle argument, but removing theExactlyOneOf
condition in favor of aConflictsWith
condition allows agents created with an activation key to be imported without requiring the attribute to be set in the corresponding Terraform configuration.An import statement can now look like:
To replace the removed functionality, an apply-time check has been added to the create operation which verifies at least one of
ip_address
oractivation_key
is set. The downside is this requirement won't be checked at plan time as before, but moving the logic here enables import to behave as expected.Relations
Closes #33458
References
Output from Acceptance Testing