Improve PostgreSQL ordering, reduce issues

[wejdross]

Fix probably a bug in our ObjectStorage spec

Checklist

• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• Update tests.
• Link this PR to related issues.

[wejdross]

@Kidswiss please take a look at this, seems that it was the issue with our services - causing broken deployment of services. After deleting that line everything seems to work.

[Kidswiss]

@Kidswiss please take a look at this, seems that it was the issue with our services - causing broken deployment of services. After deleting that line everything seems to work.

Can you elaborate what "probably a bug" you're fixing here? There's more things happening than just deleting a line.

[wejdross]

Was our intention to add this .spec.parameters.security to ObjectBuckets? I'd say no - so it's bug, but I can be wrong and miss some information - therefore "probably a bug" 😆

[Kidswiss]

Was our intention to add this .spec.parameters.security to ObjectBuckets? I'd say no - so it's bug, but I can be wrong and miss some information - therefore "probably a bug" 😆

.spec.parameters.security contains the deletion protection settings for the bucket. They are necessary or they can't delete the buckets anymore, if they use ObjectBucket directly.

[Kidswiss]

Please test on lab, so we're sure it doesn't remove any existing sgclusters.

[zugao]

Does this PR help with creating 5 or more instances at the same time?

[wejdross]

Does this PR help with creating 5 or more instances at the same time?

yes, it solves the issue

[zugao]

LGTM, again as Simon said, please test with existing buckets, we don't want those buckets to be removed accidentely.