Command to create the organisations in chef server

[sonali523]

🔩 Description: What code changed, and why?

Command to add the sample data of organisations in chef server using web ui key

⛓️ Related Resources

#6532

👍 Definition of Done

I have added changes to load the sample data of organisations in chef server
Using command we can add the sample organisations in server on chef server side using web ui key.
For script, added an API to create the organisations on chef server.
API reads the web ui key of given chef server and make request to create an organisations.

👟 How to Build and Test the Change

1. Command to add the orgs in server
   You need to enter the hab studio then check the services are running.
   To start the services you can use start_infra_proxy_service or start_all_services
   Then run infra_service_load_sample_orgs

   Options:
   -N: Number of records, default 50
   -S: Chef infra server id, which should be available on chef server and added in automate
   -O: Chef organization's name prefix, default: chef-org

   Example:
   infra_service_load_sample_orgs -N 50 -S local-dev -O chef-org

2. API to create an orgs in chef server
   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
   3. Add the organisation name and full name in the request.

   Request

   curl --location --request POST 'https://a2-dev.test/api/v0/infra/servers/{SERVERID}/infraserverorgs' \
   --header 'api-token: your admin token' \
   --header 'Content-Type: application/json' \
   --data-raw '{
     "name":"test",
     "full_name": "test chef software"
   }'
   

   Response
   {}

✅ 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

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication