-
Notifications
You must be signed in to change notification settings - Fork 3
fix: replace deprecated "profile_id" with "iam_id" in ibm_iam_trusted_profile_policy resource #211
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
base: main
Are you sure you want to change the base?
Conversation
/run pipeline |
/run pipeline |
This is an expected failure
|
/run pipeline |
|
main.tf
Outdated
for_each = local.policy_map | ||
|
||
profile_id = ibm_iam_trusted_profile.profile.profile_id | ||
iam_id = ibm_iam_trusted_profile.profile.profile_id |
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.
@iamar7 @ocofaigh Following IBM Documentation in terraform registry profile_id
is not an attribute of ibm_iam_trusted_profile resource 😄 ... What about profile_id attribute on ibm_iam_trusted_profile if ibm_iam_trusted_profile_policy resource change the profile_id by iam_id ....
https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/iam_trusted_profile
/run pipeline |
Failing with this
|
/run pipeline |
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.
@iamar7 Did you reach out to IAM provider team looking for guidance on how to migrate to the new property without a breaking change? We need to find out a way to prevent this destroy:
Address: module.trusted_profile.ibm_iam_trusted_profile_policy.policy["tp-complete-7pm-profile-0"]
Actions: [delete create]
I do not approve with the skipping of this upgrade test without a migration path to prevent destroy
The provider team have confirmed they are going to release a patch release that would prevent this being a breaking change. |
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.
Latest provider should have this fix - can we try?
As per this comment, for trusted profile provider is yet to raise a PR. |
Description
Issue - 15360
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers