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
We had some code using consul/api to create namespaces in a partition, which worked in Consul 1.11.5+ent but does not in 1.12.0+ent.
The following will create ns-1 in partition part-1 in 1.11.5+ent. With 1.12.0+ent, it creates ns-1 in the default partition. Basically, the Partition field is now being ignored, it seems.
// Ignores(?) the Partition field in 1.12.0+entns, _, err:=client.Namespaces().Create(&api.Namespace{
Partition: "part-1",
Name: "ns-1",
}, nil)
Note that specifying the partition in query parameters works in both versions, for example:
// Works in both 1.11.5+ent and 1.12.0+entns, _, err:=client.Namespaces().Create(&api.Namespace{
Name: "ns-1",
}, &api.WriteOptions{Partition: "part-1"})
Reproduction Steps
Steps to reproduce this issue:
Run Consul 1.12.0+ent (consul agent -dev ...)
Run the following script which creates a partition and namespace.
Overview of the Issue
We had some code using
consul/api
to create namespaces in a partition, which worked in Consul 1.11.5+ent but does not in 1.12.0+ent.The following will create
ns-1
in partitionpart-1
in 1.11.5+ent. With 1.12.0+ent, it createsns-1
in the default partition. Basically, thePartition
field is now being ignored, it seems.Note that specifying the partition in query parameters works in both versions, for example:
Reproduction Steps
Steps to reproduce this issue:
consul agent -dev ...
)Expand for script
The output will look like, where namespace
ns-1
is created in the default partition.Consul info for both Client and Server
Client info
Server info
Operating system and Environment details
Log Fragments
The text was updated successfully, but these errors were encountered: