Associate project for every organisation fetched

[YashviJain01]

🔩 Description: What code changed, and why?

When a organisation is migrated from the chef server to automate, an IAM project needs to be linked with it.
So added the call to project create service to create the project with the name of serverId_orgID, every time the organisation is stored in the database the project is created with the name having all the policies as editors, viewer, owner.

⛓️ Related Resources

👍 Definition of Done

Project is created and stored in database at the time of migration

👟 How to Build and Test the Change

Steps to build:

rebuild components/infra-proxy-service
rebuild components/automate-gateway

Steps to test:

1. Ensure Chef Infra Server is running. If it is not start it with start_chef_server
2. Add the chef-server test environment credentials and extract the SERVER IDs

Request
This is a get request.
curl -sSkH "api-token: $(get_admin_token)" 'https://a2-dev.test/api/v0/infra/servers/SERVER_ID/infraserverorgs'

Response

{
    "orgs": [
        {
            "id": "test",
            "name": "test",
            "admin_user": "",
            "credential_id": "",
            "server_id": "serverId",
            "projects": ["serverID_test"]
        }
    ]
}

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[m0dul3]

a

[kalroy]

authzProjectClient can be a better name of the variable?

Suggested change

	service, err := service.Start(l, migrationConfig, connFactory, secretsClient, authzClient, authzClientProject)
	service, err := service.Start(l, migrationConfig, connFactory, secretsClient, authzClient, authzProjectClient)

[YashviJain01]

Changed to the suggested name

[kalroy]

Will it create the policies too for the project?

[YashviJain01]

Yes, we are passing skip policies as false, therefore its creating project with all the policies.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
21.2% Duplication