bugfix: ZENKO 2702 Use replica set config instead of rs0

[miniscruff]

We already had the replica set value in the config and was loading it but was using a fixed rs0 in place of the real value.

[bert-e]

Hello miniscruff,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

[anurag4DSB]

Shouldn't we create development/8.2 in Arsenal?

We are planning to concentrate on only Zenko v2.x
In the future if we have a bug in Zenko v1.x and we have to update arsenal in cloud server, this might break things.

I checked the ticket and it's fix version is only 2.x so I am guessing there is nothing planned for cloudsevrer dev/8.1.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

The following reviewers are expecting changes from the author, or must review again:

• @anurag4DSB

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

[anurag4DSB]

Okay approved, after checking cloud server config and your PR summary :D.
But I think we should still make a development/8.2 for 2.x
what do you think?
CC @jonathan-gramain

[miniscruff]

Shouldn't we create development/8.2 in Arsenal?

We are planning to concentrate on only Zenko v2.x
In the future if we have a bug in Zenko v1.x and we have to update arsenal in cloud server, this might break things.

I checked the ticket and it's fix version is only 2.x so I am guessing there is nothing planned for cloudsevrer dev/8.1.

The versioning of our packages are a mystery to me, I picked 8.1 as it was the default and @rahulreddy said that was fine over slack.

[anurag4DSB]

Shouldn't we create development/8.2 in Arsenal?

We are planning to concentrate on only Zenko v2.x

In the future if we have a bug in Zenko v1.x and we have to update arsenal in cloud server, this might break things.

I checked the ticket and it's fix version is only 2.x so I am guessing there is nothing planned for cloudsevrer dev/8.1.

The versioning of our packages are a mystery to me, I picked 8.1 as it was the default and @rahulreddy said that was fine over slack.

This PR is good for 8.1. We do not have any breaking changes till now. I was considering the features we will add in the future specific to 2.x.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

The following options are set: approve

[rahulreddy]

If you ask me I would prefer 9.0 but I don't want to break RING 9 convention. Since 8.1 didn't have any breaking changes, we kept it as-is. Let me ask the question in the channel and see what everyone thinks.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

Peer approvals must include a mandatory approval from @jonathan-gramain.

[miniscruff]

/approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/8.1

The following branches will NOT be impacted:

• development/6.4
• development/7.4
• development/7.8

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/8.1

The following branches have NOT changed:

• development/6.4
• development/7.4
• development/7.8

Please check the status of the associated issue ZENKO-2702.

Goodbye miniscruff.