Fix: automatically upload config file when using WandbLogger with PTL CLI

[ayulockin]

What does this PR do?

While using the CLI, the config file is logged to W&B partially (run page). Ideally, it should log the entirety of the config for better reproducibility and comparison of experiments. This PR fixes this issue by modifying the SaveConfigCallback to execute some logic only when WandbLogger is used (run page).

To further support user convenience, the change saves the config passed to the CLI to the correct wandb/exp_name dir.

Fixes #<issue_number>

Before submitting

• Was this discussed/agreed via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist

• Is this pull request ready for review? (if not, please submit in draft mode)
• [] Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

---

📚 Documentation preview 📚: https://pytorch-lightning--19268.org.readthedocs.build/en/19268/

[codecov]

Codecov Report

Merging #19268 (7240741) into master (6bc27d5) will decrease coverage by 34%.
The diff coverage is 40%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #19268      +/-   ##
==========================================
- Coverage      83%      49%     -34%     
==========================================
  Files         445      437       -8     
  Lines       37289    37146     -143     
==========================================
- Hits        31119    18241   -12878     
- Misses       6170    18905   +12735     

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Generic High Entropy Secret	68d1169	tests/tests_data/streaming/test_resolver.py	View secret
-		Generic High Entropy Secret	68d1169	tests/tests_data/streaming/test_resolver.py	View secret
-		Generic High Entropy Secret	68d1169	tests/tests_data/streaming/test_resolver.py	View secret
-		Generic High Entropy Secret	68d1169	tests/tests_data/streaming/test_resolver.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[ayulockin]

@aniketmaurya who would be the right person to review this PR. :)

[ayulockin]

Hey @awaelchli, was curious if you can take a look at this PR. Thanks 🌮

[awaelchli]

Hey @ayulockin

Sorry for the very late review, it's very busy atm.

I think it's a good idea, and this will also be useful for the other loggers. Let's do it.
I left a design suggestion below.

[awaelchli]

The code below looks good in general.
However, this save_config hook is meant to be overridden by users who want to add their own saving logic. We should not implement it here. I propose to simply create a new callback:

class LoggerSaveConfigCallback(SaveConfigCallback)
    def save_config(...):
        # your logic here

and then we register that one by default if the CLI is used.

What do you think?