Skip to content

chore(cli): rename LegacyClientEnabled to FutureClientEnabled - #1029

Open
francescobrivio wants to merge 1 commit into
DIRACGrid:mainfrom
francescobrivio:rename_LegacyClientEnabled
Open

chore(cli): rename LegacyClientEnabled to FutureClientEnabled#1029
francescobrivio wants to merge 1 commit into
DIRACGrid:mainfrom
francescobrivio:rename_LegacyClientEnabled

Conversation

@francescobrivio

Copy link
Copy Markdown
Contributor

PR Description

Addressing #504.
As suggested in the issue I've simply renamed LegacyClientEnabled to FutureClientEnabled.

PR Validation

Local tests (pixi run pytest-diracx-cli) are successful.

Further Considerations

From a quick search in DIRACGrid github I see that LegacyClientEnabled also appears in:

  1. https://github.com/DIRACGrid/DIRAC/blob/917fff7f37788c4558e1a19f5bd53e6196f0235c/tests/Jenkins/dirac-cfg-setup-diracx.py#L76-L86
  2. https://github.com/DIRACGrid/DIRAC/blob/917fff7f37788c4558e1a19f5bd53e6196f0235c/src/DIRAC/ConfigurationSystem/Client/PathFinder.py#L251

Should I update those as well (in a separate PR)?

@aldbr

aldbr commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Should I update those as well (in a separate PR)?

Yes, and you can do so within this PR 🙂
Thanks!

@aldbr aldbr linked an issue Sep 3, 2026 that may be closed by this pull request
@francescobrivio

Copy link
Copy Markdown
Contributor Author

and you can do so within this PR 🙂 Thanks!

But those two files are in DIRAC not in diracx repo, so I guess I'll need to do a separate PR. I'm preparing it!

@aldbr

aldbr commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Oops indeed, I read too fast, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename LegacyClientEnabled in the CS to FutureClientEnabled

2 participants