Order of repositories in docker repository group is not respected about terraform-provider-nexus HOT 8 OPEN

It's the same bug for the other type of groups, like npm and maven.

from terraform-provider-nexus.

I can confirm that this problem still exists. Looking into it.

from terraform-provider-nexus.

I´ve checked this and the issue seems to be in this schema attribute since TypeSet is used to represent an unordered collection of items. Terraform doc reference: https://developer.hashicorp.com/terraform/plugin/sdkv2/schemas/schema-types#typeset

We would need to use TypeList to preserver the order I believe

from terraform-provider-nexus.

The problem still exists in the latest provider version

from terraform-provider-nexus.

I can confirm that the problem still exists in version 2.1.0 of the datadriver, and this also affects ALL kind of groups (not just docker). The underlying issue was well pointed out in the comments above:
The datadriver implementation uses a set, not a list, and therefore the ordered input gets reshuffled along the way.

Environment (although irrelevant due to the nature of this bug): Terraform 1.7.1 and Nexus RM Pro 3.62.0-01.

from terraform-provider-nexus.

first, it is only fixed for docker groups

from terraform-provider-nexus.

we will implement the same way for all repository types if someone can approve that the problem is fixed in version https://github.com/datadrivers/terraform-provider-nexus/releases/tag/v2.2.0

from terraform-provider-nexus.

The merged PR applies to the base repository schema so it applied to all repository types.

This is working as expected for an npm repo:

• I applied the terraform
• I logged into my instance and altered the group member order using the GUI
• I reapplied the terraform
• The GUI shows that my manual order change was reverted and the ordering is now as desired

from terraform-provider-nexus.