You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# nexus_repository_apt_hosted.my_repo will be updated in-place~ resource "nexus_repository_apt_hosted""my_repo" {
id = "my-repo"
name = "my-repo"# (2 unchanged attributes hidden)
+ signing {
+ keypair = (sensitive value)
+ passphrase = (sensitive value)
}
# (2 unchanged blocks hidden)
}
Expected Behaviour
It seems as if the signing block would be added (not modified), even though it is present in the config. The variables are set to the same values as they are in Nexus.
Looking into the apt hosted data source code, it appears the data source does not handle aptSigning data from Nexus at all. The related data source test has signing data populated in its fixture, but it's not tested.
Actual Behaviour
Signing block not marked for creation/modification.
Steps to Reproduce
terraform plan
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Terraform Version
1.6.5
Nexus Provider Version
1.22.0
Nexus Version
3.61.0
Affected Resource(s)/Data Source(s)
repository_apt_hosted
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
It seems as if the signing block would be added (not modified), even though it is present in the config. The variables are set to the same values as they are in Nexus.
Looking into the apt hosted data source code, it appears the data source does not handle
aptSigning
data from Nexus at all. The related data source test has signing data populated in its fixture, but it's not tested.Actual Behaviour
Signing block not marked for creation/modification.
Steps to Reproduce
terraform plan
References
No response
The text was updated successfully, but these errors were encountered: