giseldo/neodataset huggingface dataset:
original filename is wrongly stored in par2 file (lp:#1689324)

[Original report](https://bugs.launchpad.net/bugs/1689324) created by **Marian Sigler (maix42)**
```
Since a while (I don't exactly know which version since I skipped some
versions due to another bug) when using par2 (specifically, I use
par2+pexpect+sftp://), the filename given to par2 includes a path
(archive_dir/.../$filename.gpg instead of just $filename.gpg), which causes
this error

File is corrupt. Try to repair duplicity-
inc.20170418T124107Z.to.20170425T125712Z.manifest.gpg
Failed to repair duplicity-
inc.20170418T124107Z.to.20170425T125712Z.manifest.gpg


Demonstrated running `strings` on the par2 files (NAME is the `--name`
parameter, obfuscated for privacy; `cache/` is my `--archive-dir`)

earlier (good)
duplicity-inc.20170204T171430Z.to.20170221T140208Z.manifest.gpg.par2:
duplicity-inc.20170204T171430Z.to.20170221T140208Z.manifest.gpg
duplicity-inc.20170221T140208Z.to.20170403T131919Z.manifest.gpg.par2:
duplicity-inc.20170221T140208Z.to.20170403T131919Z.manifest.gpg

now (bad)
duplicity-inc.20170418T124107Z.to.20170425T125712Z.manifest.gpg.par2:
cache/NAME/duplicity_temp.1/duplicity-
inc.20170418T124107Z.to.20170425T125712Z.manifest.gpg
duplicity-inc.20170425T125712Z.to.20170508T143651Z.manifest.gpg.par2:
cache/NAME/duplicity_temp.1/duplicity-
inc.20170425T125712Z.to.20170508T143651Z.manifest.gpg



par2cmdline version 0.7.0
duplicity 0.7.12
Linux 4.10.11-1-ARCH x86_64 GNU/Linux
```

Story points: 6.0
Split out verify and compare-data commands (and remove target for verify) (lp:#1688657)

[Original report](https://bugs.launchpad.net/bugs/1688657) created by **Aaron Whitehouse (aaron-whitehouse)**
```
As per:
http://lists.gnu.org/archive/html/duplicity-talk/2017-01/msg00065.html

"I would imagine that a more readily understandable syntax would be a
duplicity "verify" command with just one argument (duplicity verify ...
source_url), and another duplicity "compare" command that would take two
arguments (duplicity compare ... source_url target_directory [--compare-
data]) and compare backup against the target_directory's files size/date
and optionally content (when used with --compare-data)."

I agree. I am about to do some work on the command line parsing side (Bug
#1480565), so can add this to my list.

As ede said in that thread, the verify command has evolved unhelpfully over
time and the need for a target in verify is a hangover from that.
```

Story points: 8.0
duplicity shouldn't sync so much (lp:#1686643)

[Original report](https://bugs.launchpad.net/bugs/1686643) created by **Martin Nowak (dawgfoto)**
```
Too many commands of duplicity first sync manifests and signatures to the
local cache, even though they could just work with remote data.
Since signature files can become multiple GB, this is fairly annoying, e.g.
when checking collection-status from a dev machine or before removing old
backups.
Syncing should only be done when it's necessary, or alternatively there
should be at least an option to skip syncing.
```
Original tags: enhancement

Story points: 10.0
Provide pip package (lp:#1685784)

[Original report](https://bugs.launchpad.net/bugs/1685784) created by **Yajo (yajo)**
```
Installing duplicity is awesomely hard because one has to guess
dependencies to get all plugins working.

Please add ability to do `pip install duplicity` and get a fully working
and updated duplicity system.
```

Story points: 6.0
error uploading manifest file on incremental backup (lp:#1674833)

[Original report](https://bugs.launchpad.net/bugs/1674833) created by **ljesmin (lauri-jesmin)**
```
Have a problem with duplicity incremental backups to S3.

I do backup from about 30 G of small files, with exclusion of some files by
pattern to S3, eu-central-1 bucket.

I use duplicity 0.7.11 from EPEL on CentOS 7.3. Python is 2.7.5.

Full backups work fine, but incremental backups immediately after full
backup
generate errors.

Full backup command line:

duplicity full --no-encryption --s3-use-multiprocessing
--s3-multipart-chunk-size 10 --num-retries 5 --exclude "**typo3temp/**"
--exclude "**_temp/**" --exclude "**_processed_/**" /var/www
"s3://s3.eu-central-1.amazonaws.com/backup-bucket-name/www"

Incremental backup command line:

duplicity incremental --no-encryption --s3-use-multiprocessing
--s3-multipart-chunk-size 10 --num-retries 5 --exclude "**typo3temp/**"
--exclude "**_temp/**" --exclude "**_processed_/**" /var/www
"s3://s3.eu-central-1.amazonaws.com/backup-bucket-name/www"

Output on erratic incremental backup:

Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sun Mar 19 02:15:10 2017
Giving up after 1 attempts. OSError: [Errno 2] No such file or directory:
'/root/.cache/duplicity/652b29dc986d2c5850695bd80bf5261a/duplicity-inc.
20170319T001510Z.to.20170321T001455Z.manifest'

After backup, in /root/.cache/duplicity/652b29dc986d2c5850695bd80bf5261a/
there
are such files:

duplicity-full.20170319T001510Z.manifest
duplicity-new-signatures.20170319T001510Z.to.20170321T001455Z.sigtar.gz
duplicity-inc.20170319T001510Z.to.20170321T001455Z.manifest.part

In AWS bucket are from latest backup such files:

www/duplicity-inc.20170319T001510Z.to.20170321T001455Z.vol1.difftar.gz
www/duplicity-new-signatures.20170319T001510Z.to.20170321T001455Z.sigtar.gz

And manifest file is missing.

Seems that for some reason, manifest is created as .part file and upload
function does not use this file.
```

Story points: 6.0
Unicode characters in filenames are not restored correctly (lp:#1672077)

[Original report](https://bugs.launchpad.net/bugs/1672077) created by **Zachs Kappler (jet-metalsonic500)**
```
While restoring my music folder, I noticed that files or folders with
Unicode characters in their names are being restored just fine, but their
Unicode characters in the filename get replaced with the code used to
represent them.

An example of what is happening:
Original Filename: Gangnam Style (강남스타일)
Restored Filename: Gangnam Style (uac15ub0a8uc2a4ud0c0uc77c)

Additionally, it only happens to the files I have that contain Japanese or
Korean characters, but not symbols such as ♥ or ♘.

I am using deja-dup 34.2-0ubuntu1.1 on elementaryOS 0.4
```

Story points: 6.0
GPG Key Handling (lp:#1670151)

[Original report](https://bugs.launchpad.net/bugs/1670151) created by **Kenneth Loafman (kenneth-loafman)**
```
In order to provide the best security, duplicity should use the key
fingerprint when talking with the gpg process.  It should allow the user to
specify the short key (8-char), long key (16-char) and the fingerprint
(40-char) on the command line and convert to fingerprint when needed.

This follows GNU's best practices for handling keys between processes.
```

Story points: 6.0
Backend requirements are not installed (lp:#1667487)

[Original report](https://bugs.launchpad.net/bugs/1667487) created by **Adrien Delhorme (adrien-delhorme)**
```
Some backends have module dependencies (for example pyrax) that are not
installed with duplicity. There is a requirements.txt file in the project
but the setup.py does not use this it to install dependencies.

Why not pass the content of requirements.txt file to setup.py's
install_require argument, or to avoid installing all backends dependencies,
to extras_require argument?
```

Story points: 6.0
Support SGDbOps tolerations on the web console

When #1707 is done, the web console should support for setting up SGDbOps tolerations.

**Acceptance Criteria:**

* [x] Support adding tolerations to any type of SGDbOps on the web console.
* [x] List the toleration info on the op summary
* [x] List the toleration info on the op details
* [x] Test the implementation

Story points: 12.0
Support OIDC Auth for the AdminUI

<!--
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Feature Request" label.

Issue tracker:

- https://gitlab.com/ongresinc/stackgres/-/issues?label_name=Feature%20Request 
and verify the issue you're about to submit isn't a duplicate.
-->

### Problem to solve

We would like to use KeyCloak as an OIDC provider for Web Console Auth

### Further details

Context: https://stackgres.slack.com/archives/C014UGLAD9R/p1655845008957569

We are wanting to avoid using Kubernetes Secrets to enable auth to the web console. Being able to leverage an OIDC provider, in our case KeyCloak, would be killer.

### Proposal

<!-- How could we going to solve the problem? -->

### Testing

<!-- What risks does this change pose? How might it affect the quality of the product?  -->


## Acceptance Criteria
<!-- Acceptance Criteria, Definition of Done, describe the expected output -->


### Links / references

Story points: 40.0
Manual backups shouldnt delete the job when done

Backups started from the SGBackupConfig ( aka automatic backups ) don't clean the Job when completed, so logs can be reviewed afterwards, when starting a backup from the UI ( aka Manual backups ) the job is cleaned when the backup is completed, that is very annoying, the only way is to get the logs is to wait for them in real time, not a good option if the process takes long, much better to simply not clean job, so log can be reviewed later..

Story points: 4.0
Edit SGPostgresConfig form should only list custom parameters

### Summary

When editing an SGPostgresConfig from the web console, the form shows all the parameters on the configuration, including the default values which have not been set by the user, but by StackGres.

![image](/uploads/ed367bd9779c447502e6d4e29289b0a2/image.png)


### Expected Behaviour

The form should only list parameters which have been explicitly set by the user.


- StackGres version: `1.2.0`

Story points: 12.0
Simplify action buttons names on CRD Details

### Summary
CRDs Details views have a row of action buttons: `Edit`, `Clone`, and `Delete`. All those buttons are followed by the CRD Kind. This makes the actions section very verbose, specially on the Configurations:
- `Edit Configuration`
- `Clone Configuration`
- `Delete Configuration`

Since there are more action items on that same row, we should simplify the naming of these buttons. We propose removing the CRD Kind and leave just the action itself: `Edit`, `Clone`, and `Delete`.

Furthermore, on the Cluster Details view, the `Clone` button is actually named `Clone Cluster Configuration`. We propose renaming it to just `Clone`, because:
1. When the User clicks on `Clone Cluster Configuration`, a warning appears explaining that what's being cloned is the Cluster Configuration.
2. On the List views, all `Clone` icons are identical for all Kinds, and this has never felt misleading.

### Environment
- StackGres version: 1\.2.0

### Relevant logs and/or screenshots
![Screenshot_2022-06-16_at_18.51.41](/uploads/19e91e1cec8197d0305f4c6999e7581e/Screenshot_2022-06-16_at_18.51.41.png)
![Screenshot_2022-06-16_at_18.51.49](/uploads/ac3743bc296cebe7d174f05abc79bdf0/Screenshot_2022-06-16_at_18.51.49.png)

Story points: 4.0
Pods can't start in Namespaces with Resource Quotas

<!--
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Bug" label.

Issue tracker:

- https://gitlab.com/ongresinc/stackgres/-/issues?label_name=Bug

and verify the issue you're about to submit isn't a duplicate.
-->
### Summary

In Namespaces with ResourceQuotas assigned, the StatefulSet cannot start pods because not all containers have requests and limits set.

### Current Behaviour 

Pods fail to create because not all containers have requests and limits set.

#### Steps to reproduce

1. Create a Namespace
2. Create a ResourceQuota

```yaml

apiVersion: v1
kind: ResourceQuota
metadata:
  labels:
    app.kubernetes.io/instance: ttd-namespaces
  name: kpop-test-quota
  namespace: kpop-test
spec:
  hard:
    limits.cpu: 2
    limits.memory: 4Gi
    requests.cpu: 1
    requests.memory: 2Gi
```

3. Create a Cluster
4. Inspect the StatefulSet

### Expected Behaviour

The pods should be able to be scheduled.

### Possible Solution

All containers (including initContainers) should have requests and limits set.

### Environment

- StackGres version:
<!-- if you have used helm, you can use:  `helm get notes -n stackgres stackgres-operator` 
more generic: `kubectl get deployments -n stackgres stackgres-operator --template '{{ printf "%s\n" (index .spec.template.spec.containers 0).image }}'`
-->
- Kubernetes version: 1.19-1.21
- Cloud provider or hardware configuration: EKS


### Relevant logs and/or screenshots

```
  Warning  FailedCreate  4s (x104 over 42h)  statefulset-controller  create Pod pobrien-test-0 in StatefulSet pobrien-test failed error: pods "pobrien-test-0" is forbidden: failed quota: kpop-test-quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory
```

Story points: 8.0
Add in the UI support to the new minor PG version 14.4

We need to add support to a new minor version. PostgreSQL version 14.4.

We need also to add an expressive warning for each minor previous release in the 14 major. The reason is that this minor versions could generate a data corruption and different bugs that are fixed and we should be clear that is dangerous.

Acceptance criteria:
- [x] Add the support to the new minor release.
- [x] Create the Warning messages for the UI.

Story points: 4.0
Support cert-manager Certificates for the Stackgres Operator

<!--
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Feature Request" label.

Issue tracker:

- https://gitlab.com/ongresinc/stackgres/-/issues?label_name=Feature%20Request 
and verify the issue you're about to submit isn't a duplicate.
-->

### Problem to solve

We would like to use [cert-manager](https://cert-manager.io/) issued TLS certificates instead of passing our own in via values.yaml or using a self-signed certificate.

### Further details

This would considerably ease Operations on our side as we already have a working cert-manager installation in all of our clusters.

### Proposal

I think the first step would be to generate the self-signed certificates as a `kubernetes.io/tls` Secret that matches the format that cert-manager creates:

```
apiVersion: v1
data:
  ca.crt: <ca-cert>
  tls.crt: <tls-cert>
  tls.key: <tls-key>
kind: Secret
metadata:
  annotations:
  name: test-tls-cert
  namespace: test
type: kubernetes.io/tls
```

After that I believe we would want a flag in values.yaml that would allow us to easily turn off cert generation:

```
cert:
  auto_generate: true
```

I think we would also probably want to be able to name the Secret that would get volume mounted?

If you know of a workaround here I am all ears. I searched through the docs and Issues and couldn't find anything relevant.

### Testing

<!-- What risks does this change pose? How might it affect the quality of the product?  -->


## Acceptance Criteria

* [x] Allow to use an already existent secrets for both operator and REST API
* [x] Add a flag in order to create cert manager custom resources that allow to create the operator secret automatically
* [x] Tests
### Links / references

Story points: 16.0
Cluster bootstrap completed event is updated continuously

### Summary

Cluster bootstrap completed event is updated continuously.

```
Normal  ClusterBootstrapCompleted    8s (x178 over 28m)  cluster-controller  Cluster bootstrap completed                                                                                              
```

#### Steps to reproduce

1. Create a cluster

### Expected Behaviour

Cluster bootstrap completed event is create once.

### Environment

- StackGres version: 1.2.0
- Kubernetes version: ?
- Cloud provider or hardware configuration: ?

Story points: 1.0
Resource name not shown on breadcrumbs

### Summary

When browsing any resource on the web console, the breadcrumbs do not include the name of the requested resource.

![image](/uploads/487e33bb2206767e8c4f71463a870cbf/image.png)


#### Steps to reproduce

- Enter the web console
- Select any resource and click on its name to see its details
- On the resource details screen the name is not included on the breadcrumbs



### Environment

- StackGres version: `1.2.0`

Story points: 4.0
Missing service status on SGCluster and SGDistributedLogs details

### Summary

When listing services details for SGClusters and SGDistributedLogs, there's no distinction between enabled and disabled services, which might be misleading.

![image](/uploads/e9519916330549568b0103557933f35f/image.png)

![image](/uploads/73fbf5964287dbb112bbfae355beade4/image.png)


#### Steps to reproduce

* Enter the web console
* Create an SGCluster or an SGDistributedLog disabling either the Primary or Replicas service
* Enter the resource details
* The service is shown regardless of its status, but the later is not shown at all


### Expected Behaviour

Services statuses should always be shown


### Environment

- StackGres version: `1.2.0`

Story points: 2.0
Change text of Close Details button

### Summary
On the web console, CRD details sections have a `Close Details` button. The `Close Details` button redirects to the List view of the parent Kind. The text of the button can be misleading, since the User may think it literally closes the details view, in the sense of it redirects back to the previous page. The text of the button should be improved to make it clear it will show the List view of the parent Kind. 

Text proposal: `Go to [kind] List`

### Environment
- StackGres version: 1\.2.0

Story points: 2.0
Boolean specs in negative should be expressed in positive

### Summary
On the web console, there are boolean specs that are expressed in negative (e.g. `Disable Metrics Exporter`, `No Kill Backend`). Some of them are expressed in a 'reverse' manner (in positive, i.e. `Metrics Exporter`), but others are not. All specs expressed in negative should be expressed in positive.

### Environment
- StackGres version: 1\.2.0

Story points: 8.0
Wait Timeout on Repack databases appears empty

### Summary
When adding databases to a Repack operation, the `Wait Timeout` field appears empty on all databases after the first one.

#### Steps to reproduce
1. Go to `Create DbOps` and select `Repack`.
2. Enable `Database Specific Options`.
3. Add a new database.
4. The `Wait Timeout` field of the new database appears empty.

### Expected Behaviour
The default value of `Wait Timeout` should be `Inherit from global settings`.

### Environment
- StackGres version: 1\.2.0

### Relevant logs and/or screenshots
![Screenshot_2022-06-13_at_12.30.53](/uploads/49ea9802dab5b558b3c0635e294e665b/Screenshot_2022-06-13_at_12.30.53.png)

Story points: 6.0
Fix specs display on details views

### Summary
Some specs of the details view need to be fixed:
- Major Version Upgrade details: Backup Path appears even if it has no value.
- Cluster details: Cluster Pod Anti Affinity only appears if disabled.
- Logs Server details: Cluster Pod Anti Affinity only appears if disabled. 

### Environment
- StackGres version: 1\.2.0

Story points: 2.0
Close Details should return to previous screen

### Summary
`Close Details` button redirects to the List view of the CRD, instead of showing the previous screen.


#### Steps to reproduce
1. Go to any Cluster Details.
2. Click on the eye icon of any CRD (e.g. the Instance Profile).
3. The eye icon opens the Details view of that specific CRD (in this case, the details of the Instance Profile).
4. Click on `Close Details`.
5. The User is redirected to the List view of that CRD (in this case, the Instance Profiles List), instead of returning to the previous screen (in this case, Cluster Details).

### Expected Behaviour
When clicked on `Close Details` the details should close and show the previous screen.

### Possible Solution
Make `Close Details` behave as the `Cancel` button on the forms.

### Environment

- StackGres version: 1\.2.0

Story points: 2.0
Support topologySpreadConstraints for SGCluster

### Problem to solve

Support [`topologySpreadConstraints`](https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/) in the `SGCluster` custom resource.

### Proposal

Proposed section to map to `.spec.template.spec.topologySpreadConstraints` section of generated `StatefulSet`:

```yaml
apiVersion: stackgres.io/v1
kind: SGCluster
spec:
  pods:
    scheduling:
      topologySpreadConstraints: [ <object> ] # the same as https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#topologyspreadconstraint-v1-core
```

## Acceptance Criteria

* [ ] Implement the change in the SGCluster CRD
* [ ] Implement the change in the REST API
* [ ] Tests
* [ ] Documentation

### Links / references

* https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#topologyspreadconstraint-v1-core

Story points: 8.0
Remove support for StackGres 1.0

Remove support for StackGres version 1.0. In particular:

* [ ] Remove code that support StackGres version 1.0 in the reconciliation cycle.
* [ ] Remove code that support StackGres version 1.0 in the webhooks.
* [ ] Remove code that support StackGres version 1.0 in the E2E tests.
* [ ] When upgrading the helm chart from StackGres 1.0 an error will be showed and the upgrade must fail.
* [ ] Upgrading from StackGres 1.0 or any other previous version, including alpha and beta version may be performed if value `forceUpgradeFromUnsupportedVersion` is set to `true`. The message when trying to upgrade from an unsupported version have to mention that it is possible to perform the upgrade using the `forceUpgradeFromUnsupportedVersion` value but has the drawback that the cluster will not be reconciled anymore and some operation may stop working until the user performs a security upgrade database operation.

Story points: 8.0
Unify switches texts on forms

### Summary
We should unify switches texts. Right now we use ON/OFF and YES/NO. We should use `ENABLE: YES/NO` in all switches on all forms.

### Environment

- StackGres version: 1\.2.0

### Relevant logs and/or screenshots
![image-1](/uploads/181d84bb8c2e7bc362213b976c679f8c/image-1.png)

Story points: 8.0
Namespaces Overview header appears when logged out but won't show on login

### Summary

On the web console, when users log in successfully, they are taken to the "Namespaces Overview" section, but there's no header shown on top of the namespaces' cards.

![image](/uploads/bf7a6c906846650088506e86272fa544/image.png)


Also, once the user has navigated through different sections and goes back to the "Namespaces Overview". If the user logs out of the web console, the "Namespaces Overview" header still appears on top of the login form.

![image](/uploads/ac61c7ca3d1d73b0e21220ceec010bcc/image.png)



#### Steps to reproduce

- Login to the web console
- The "Namespaces Overview" section loads with no header on top (which is wrong)
- Navigate to any other section 
- Head back to the "Namespaces Overview" section by clicking on the StackGres logo
- The "Namespaces Overview" header appears (which is right)
- Logout of the web console
- The "Namespaces Overview" header still appears (which is wrong)


### Expected Behaviour

The behavior on every header on the web console should be consistent. They should always appear when logged in and should never be shown when logged out


### Environment

- StackGres version: `1.2.0`

Story points: 2.0