-
Notifications
You must be signed in to change notification settings - Fork 108
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
realm_attributes is not updating when terraform config changes #1104
Comments
I thought about destroy then recreate, but this actually can't work for me. deleting the group will invalidate:
|
@richardmcsong Thanks for the report. This looks like a bug in the REST API. I'll open a bug report internally. |
@richardmcsong The What's your use case that needs to set this field? |
@richardmcsong Just noticed that in your previous comment, your The current group resource in this provider is still using the old, deprecated Artifactory API. This old API allows Our plan is to add a new group resource to the Platform provider that uses that Access API, and deprecate the resource in this provider. |
Hey @alexhung! Sorry I must've missed these messages. I'm confused as to how I'm supposed to be configuring my LDAP synced groups if not through I see that only |
@richardmcsong The ability to automatically import LDAP settings is pending currently (I'm waiting for a bug fix in the JFrog Access service). See this discussion. |
This is my case: jfrog/terraform-provider-platform#159 |
Describe the bug
When the LDAP
realm_attributes
string is updated on theartifactory_group
resource, the plan reports that the realm string will be updated, but the realm
string is not actually updated.
Apply, then edit the realm_attribute string.
Expected behavior
Th edit should be persisted on the end server. Instead, the edit is not completed, and then it calculates the same edit on the next run.
Additional context
Artifactory version: 7.90.8
provider version = "~> 11.0"
terraform version = terraform 1.8.4
Findings
When trying to PATCH an LDAP group, it doesn't actually allow for you to update
realm_attributes
, despite what the documentation says: Updates an Access group's external ID, realm, or realm attributes.A GET request after confirms that the
realm_attributes
was not edited.The text was updated successfully, but these errors were encountered: