Create production deploy yml

[kirkkwang]

⚠️ Make copy of staging-deploy.tmpl.yaml for prod

2fd632d

This commit will simply copy the staging-deploy.tmpl.yaml file to
production-deploy.tmpl.yaml. In the next commit we can more easily
track the changes.

Update production-deploy.tmpl.yaml

5bf7447

This commit will bring over values from the current
production-deploy.yaml file on pals production.

Update deploy production.yaml per Rob's feedback

67d07e7

• Sets resource limits
• renames nameOverride to follow convention
• BACKTRACE => false
• fcrepo enabled => false

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15385149	Triggered	Generic Database Assignment	2fd632d	ops/production-deploy.tmpl.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}