Add extended attribute to get-cluster-status

[arif-ali]

This changes from the default boolean that was being used internally to what mysql expects. The values between 0 and 3 are valid.

Issue

Would like to get extra cluster status attributes to debug issues with mysql replication.

Solution

The solution allows us to do this via actions, rather than logging in, and getting the data manually

[codecov]

Codecov Report

Attention: Patch coverage is 25.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 66.30%. Comparing base (2bd2bcc) to head (27d86ed).
Report is 2 commits behind head on main.

Files	Patch %	Lines
lib/charms/mysql/v0/mysql.py	28.57%	5 Missing ⚠️
src/upgrade.py	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #428      +/-   ##
==========================================
- Coverage   66.39%   66.30%   -0.09%     
==========================================
  Files          17       17              
  Lines        3169     3173       +4     
  Branches      419      420       +1     
==========================================
  Hits         2104     2104              
- Misses        930      934       +4     
  Partials      135      135              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[paulomach]

Hi @arif-ali,

thank you for your contribution.
Please, check comments

[taurus-forever]

Thank you for the contribution here!
@paulomach will we copy to K8s ourself or should we ask @arif-ali ?

we do it

[paulomach]

lgtm

[sinclert-canonical]

👋🏻 Are these changes still desired? They got approved one year ago, despite Shayan's request to bump the lib version.

[arif-ali]

Yeah, these would still be useful to have, I'm surprised even with the approvals it never got merged; and now we have conflicts

[sinclert-canonical]

I can probably help with that, this PR seems like a low hanging fruit everyone was onboard with. Although, if we are going to do it right, the same changes should be proposed both in K8s and VM substrates.

[sinclert-canonical]

@arif-ali could you open a similar PR on mysql-k8s-operator repository?