Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Maximum Number of Accounts under task.platform.cloudfoundry.accounts #5932

Open
DanFrei opened this issue Sep 11, 2024 · 1 comment
Labels
status/need-feedback Calling participant to provide feedback

Comments

@DanFrei
Copy link

DanFrei commented Sep 11, 2024

Description:
Problem: Issue with Maximum Number of Accounts under: "task.platform.cloudfoundry.accounts"
We use SCDF for managing tasks and we're experiencing an issue with Spring Cloud Data Flow where adding more than 23 entries under "task.platform.cloudfoundry".
When adding more than 23 account, the newly added accounts/platforms would not be added (do not appear in the UI nor retrieved by the API).
We couldn't find any hard limitation for the amount of acconts in the documentation.

Further details:

Current Configuration: I have configured 27 accounts under task.platform.cloudfoundry.accounts.
Problem: Only 23 accounts appear in the Spring Cloud Data Flow UI. The remaining accounts are not displayed, nor are they accessible.
Impact: We manage many Cloud Foundry accounts and need all of them available for our Spring Cloud Data Flow server. This limitation is blocking us from running tasks on certain accounts.

Request:

Could you please confirm if there is a hard limit on the number of entries allowed under "task.platform.cloudfoundry.accounts"?
If such a limit exists, is there a way to increase the allowed number of accounts via configuration, or would a code fix be necessary to support a larger number of accounts?
Any guidance or workaround for this issue would be appreciated.

Release versions:
Spring Cloud Data Flow version: 2.11.3
Environment: Cloud Foundry

Example manifest yml to explain how we configure the accounts:

`spring-application-yaml:
 .
 .
 .
  spring.cloud.dataflow:
    task.platform.cloudfoundry.accounts:
      default:
        connection:
          url: (( .context.imports.cf.cc.srv_api_uri ))
          org: (( .context.product_config.uas_org "%UAS_DEV_SUFFIX%" ))
          space: (( .context.product_config.uas_space "%UAS_DEV_SUFFIX%" ))
          domain: (( .context.imports.cf.deprecated.app_domain ))
          username: CF_DATA_FLOW_USER
          password: ${vcap.services.uas-scdf-user-credentials.credentials.uas_dataflow_password.password}
          loginHint: (( .context.config.scdf_login_hint || "%7B%22origin%22%3A%22uaa%22%7D" ))
          skipSsValidation: false
        deployment:
          services: uas_credentials, uas-data-flow-server, uas-dataflow-postgres %OPTIONAL_BOUND_SERVICES%
          apiTimeout: 1200
          buildpacks: java_buildpack
     account-1:
        connection:
          url: (( .context.imports.cf.cc.srv_api_uri ))
          org: (( .context.product_config.uas_org "%UAS_DEV_SUFFIX%" ))
          space: (( .context.product_config.uas_space "%UAS_DEV_SUFFIX%" ))
          domain: (( .context.imports.cf.deprecated.app_domain ))
          username: CF_DATA_FLOW_USER
          password: ${vcap.services.uas-scdf-user-credentials.credentials.uas_dataflow_password.password}
          loginHint: (( .context.config.scdf_login_hint || "%7B%22origin%22%3A%22uaa%22%7D" ))
          skipSsValidation: false
        deployment:
          services: uas_credentials, uas-data-flow-server, uas-dataflow-postgres %OPTIONAL_BOUND_SERVICES%
          apiTimeout: 1200
          buildpacks: java_buildpack   
     account-2:
        connection:
          url: (( .context.imports.cf.cc.srv_api_uri ))
          org: (( .context.product_config.uas_org "%UAS_DEV_SUFFIX%" ))
          space: (( .context.product_config.uas_space "%UAS_DEV_SUFFIX%" ))
          domain: (( .context.imports.cf.deprecated.app_domain ))
          username: CF_DATA_FLOW_USER
          password: ${vcap.services.uas-scdf-user-credentials.credentials.uas_dataflow_password.password}
          loginHint: (( .context.config.scdf_login_hint || "%7B%22origin%22%3A%22uaa%22%7D" ))
          skipSsValidation: false
        deployment:
          services: uas_credentials, uas-data-flow-server, uas-dataflow-postgres %OPTIONAL_BOUND_SERVICES%
          apiTimeout: 1200
          buildpacks: java_buildpack  
          
          .
          .
          .
          .
          
   account-24:
        connection:
          url: (( .context.imports.cf.cc.srv_api_uri ))
          org: (( .context.product_config.uas_org "%UAS_DEV_SUFFIX%" ))
          space: (( .context.product_config.uas_space "%UAS_DEV_SUFFIX%" ))
          domain: (( .context.imports.cf.deprecated.app_domain ))
          username: CF_DATA_FLOW_USER
          password: ${vcap.services.uas-scdf-user-credentials.credentials.uas_dataflow_password.password}
          loginHint: (( .context.config.scdf_login_hint || "%7B%22origin%22%3A%22uaa%22%7D" ))
          skipSsValidation: false
        deployment:
          services: uas_credentials, uas-data-flow-server, uas-dataflow-postgres %OPTIONAL_BOUND_SERVICES%
          apiTimeout: 1200
          buildpacks: java_buildpack       
        '

Thank you for your help!
Best regards,
Daniel Fridman,
[email protected]

@github-actions github-actions bot added the status/need-triage Team needs to triage and take a first look label Sep 11, 2024
@ilayaperumalg
Copy link
Contributor

Hi @DanFrei , Thanks for reporting the issue.

We don't have any specific limit on the maximum number of accounts for the task platforms. Also, the task platform accounts I just checked replicating the issue by setting about 30 task platform accounts and I could see the accounts listed in both shell and the dashboard UI.

It would be helpful to investigate this further if you can add some additional information including the logs (especially, the startup log of SCDF server which initialises the task platform accounts at the startup) and any other logging information when you query the task platform list.

Thanks!

@cppwfs cppwfs added status/need-feedback Calling participant to provide feedback and removed status/need-triage Team needs to triage and take a first look labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/need-feedback Calling participant to provide feedback
Projects
None yet
Development

No branches or pull requests

3 participants