Skip to content

fix(CS): rename LegacyClientEnabled to FutureClientEnabled - #8772

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

fix(CS): rename LegacyClientEnabled to FutureClientEnabled#8772
francescobrivio wants to merge 1 commit into
DIRACGrid:integrationfrom
francescobrivio:rename_LegacyClientEnabled

Conversation

@francescobrivio

Copy link
Copy Markdown

PR Description

Addressing DIRACGrid/diracx#504 and immediate follow-up to DIRACGrid/diracx#1029: the LegacyClientEnabled has been renamed to FutureClientEnabled in diracx so in this PR I'm making the same changes in DIRAC.

Open questions:

  1. in tests/Jenkins/dirac-cfg-setup-diracx.py there are several references to legacy, should I rename them to future (changes should be transparent) ?
  2. in src/DIRAC/ConfigurationSystem/Client/PathFinder.py the change from Legacy to Future is inside a method named useLegacyAdapter, should the method be renamed as well?

BEGINRELEASENOTES

*ConfigurationSystem
CHANGE: rename LegacyClientEnabled to FutureClientEnabled

ENDRELEASENOTES

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.

1 participant