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

[RFE] Default credentials #211

Open
rromannissen opened this issue Dec 5, 2024 · 1 comment
Open

[RFE] Default credentials #211

rromannissen opened this issue Dec 5, 2024 · 1 comment
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@rromannissen
Copy link
Contributor

What is the problem?

Credentials need to be manually assigned to applications once they are created/imported.

Why is this a problem?

In a common enterprise scenario, application repositories are secured. That means that in a large application import, considering that credentials can't be included in the CSV file, the first discovery operation will fail until the user manually associates credentials with each application. This introduces a manual step in a process that should be as automated as possible to tackle large application portfolios effectively and start surfacing information as early as possible.

A different scenario that makes this more of a problem would be related to application discovery, as it would be important to automate the insights collection as much as possible as soon as applications are discovered if the source platform contained information about the application repository.

Proposed solution

Allow Administrators to define default credentials that will be automatically associated to all applications, including all newly created ones. This should follow some rules:

  • There can only be one default credential per credential type.
  • Once a credential is set as default, it will be implicitly associated to all applications that don't have a credential of that type explicitly associated.
  • UI should be explicit about default credentials being used by an application.

This could add more automation on the import and insights surfacing process by enabling a flow like the following:

  1. Applications are imported or created.
  2. Default credentials are associated to newly created applications.
  3. Language and technology discovery are executed.
  4. Based on the technology stack, applications are automatically associated to archetypes.
@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 5, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. label Dec 5, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Dec 5, 2024
@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant