Add Noble base for Pgbouncer

[dragomirp]

Pgboucer needs to probide a 24.04 base to be able to subordinate within Noble principal charms.

Will require switching to charmcraft 3.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-6152.

This message was autogenerated

[taurus-forever]

@mnmnk43434 nice try! Impressive AI level! Unfortunately cannot be merged as broken:

12:15:45 ✔ taurus:~$ charmcraft version
charmcraft 3.2.1                                                                                                                                                                                                                                       

12:15:54 ✔ taurus:/tmp$ git clone https://github.com/mnmnk43434/canonical-pgbouncer-operator-426
Cloning into 'canonical-pgbouncer-operator-426'...
...

12:16:27 ✔ taurus:(main)/tmp/canonical-pgbouncer-operator-426$ git checkout 40da1aab133df5d15d87185d0ba05dd7838824da
Note: switching to '40da1aab133df5d15d87185d0ba05dd7838824da'.
...
HEAD is now at 40da1aab Add Ubuntu 24.04 base and update to Charmcraft 3 syntax


12:16:31 ✔ taurus:((40da1aab...))/tmp/canonical-pgbouncer-operator-426$ charmcraft pack <<<<<<<<<< test yourself here.
Fields in charmcraft.yaml cannot be duplicated in metadata.yaml                                                                                                                                                                                        
Recommended resolution: Remove the duplicate fields from metadata.yaml.                                                                                                                                                                                
Full execution log: '/home/taurus/.local/state/charmcraft/log/charmcraft-20241205-121638.401513.log'                                                                                                                                                   

12:16:38 ✘ taurus:((40da1aab...))/tmp/canonical-pgbouncer-operator-426$ cat /home/taurus/.local/state/charmcraft/log/charmcraft-20241205-121638.401513.log
2024-12-05 12:16:38.402 Starting charmcraft, version 3.2.1
2024-12-05 12:16:38.402 Log verbosity level set to BRIEF
2024-12-05 12:16:38.402 Configuring application...
2024-12-05 12:16:38.402 Preparing application...
2024-12-05 12:16:38.420 Build plan: platform=None, build_for=None
2024-12-05 12:16:38.422 Loading project file '/tmp/canonical-pgbouncer-operator-426/charmcraft.yaml'
2024-12-05 12:16:38.441 Fields in charmcraft.yaml cannot be duplicated in metadata.yaml
2024-12-05 12:16:38.441 Detailed information: Duplicate fields: 'name'
2024-12-05 12:16:38.441 Recommended resolution: Remove the duplicate fields from metadata.yaml.
2024-12-05 12:16:38.441 Full execution log: '/home/taurus/.local/state/charmcraft/log/charmcraft-20241205-121638.401513.log'

Can you improve your changes to continue supporting both amd and arm architectures and stay compatible with data-platform shared workflows?

Continue growing and contributing Canonical! ;-)