fix(prod): use 'prod' environment name instead of 'production'

[boorad]

Summary

• Renames the GitHub Actions environment from production to prod in the deploy workflow to match the naming convention used by dev and stage workflows.

Environments affected

• prod (workflow only — no policy changes)

Changes

• Updated environment: fields in both dry-run and deploy jobs from production to prod
• Updated concurrency group from deploy-production to deploy-prod
• Fixed all comments to consistently reference prod instead of production

Testing

• No OPA policy changes — no opa test needed
• Verify the GitHub repository environment has been renamed from production to prod in repo settings before merging

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated deployment pipeline configuration naming conventions for consistency across the production environment settings.

[amazon-q-developer]

Review Summary

This PR correctly standardizes the environment name from production to prod throughout the workflow file, aligning with the naming convention used in deploy-dev.yml and deploy-stage.yml. All changes are consistent and complete:

• Comments updated to reference prod consistently
• Concurrency group renamed to deploy-prod
• GitHub environment references updated in both dry-run and deploy jobs
• EnforceAuth deploy-action environment parameters updated

Critical prerequisite: Ensure the GitHub repository environment has been renamed from production to prod in repository settings before merging to avoid workflow failures.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 12de7628-992b-4895-8e09-828f6d2aed6f

📥 Commits

Reviewing files that changed from the base of the PR and between 0f706c0 and 5f71913.

📒 Files selected for processing (1)

• .github/workflows/deploy-prod.yml

---

📝 Walkthrough

Walkthrough

The production deployment workflow configuration is updated to standardize environment naming from "production" to "prod" across concurrency groups, EnforceAuth action inputs, and job environment settings. Control flow and conditions remain unaffected.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/deploy-prod.yml	Updated environment naming from production to prod in concurrency group, EnforceAuth action inputs, and job environment settings for both dry-run and deploy jobs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A prod name now shines so bright,
Where "production" once held might,
Workflows dance with shorter grace,
A tidier, swifter naming space!
Our pipelines hop with fresh delight! 🐇✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: renaming the production environment from 'production' to 'prod' in the GitHub Actions workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/prod-environment-name

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}