provision-project-environment

name	provision-project-environment
description	Provision a new IRIS project environment: two databases, a namespace, a user, and a web application — verifying each step before the next, with rollback notes.

Provision Project Environment

Project: <projectName>

Verify EACH step succeeded (inspect the tool result) before proceeding to the next. If any step fails partway through, roll back the steps already completed (see the rollback note after each step) rather than leaving a half-provisioned environment.

1. Call iris_database_manage action 'create' with name: "<projectName>DATA" and a directory for the DATA database. Rollback: iris_database_manage action 'delete' with name: "<projectName>DATA".
2. Call iris_database_manage action 'create' with name: "<projectName>CODE" and a directory for the CODE database. Rollback: iris_database_manage action 'delete' with name: "<projectName>CODE".
3. Call iris_namespace_manage action 'create' with name: "<projectName>", dataDatabase: "<projectName>DATA", codeDatabase: "<projectName>CODE". Rollback: iris_namespace_manage action 'delete' with name: "<projectName>", then undo steps 1-2.
4. Call iris_user_manage action 'create' with a name and password for the project's service/developer account, and namespace: "<projectName>" as its default namespace. Rollback: iris_user_manage action 'delete' with the same name.
5. Call iris_webapp_manage action 'create' with a name starting with '/' (e.g. '/api/'), namespace: "<projectName>", and (if applicable) a dispatchClass. Note: creating a web app does NOT notify the CSP gateway — it requires saving through the Management Portal or a gateway restart to become active. Rollback: iris_webapp_manage action 'delete' with the same name.
6. Summarize what was created (database names, namespace, user, web app path) and any manual follow-up needed (CSP gateway activation for the new web app).