chore: initial Tiltfile

[bodymindarts]

Running:

buck2 run //dev:up

Will bring up tilt and starts the core / auth stack - enough to be able to develop the consent app and run its integration tests on top of it.

To verify integration tests you can either click on the consent-test resource in the tilt panel or run:

buck2 test //apps/consent:cypress

once the whole tilt file is running.

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets 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 secrets in your pull request

GitGuardian id	Secret	Commit	Filename
6464023	Generic Private Key	8f0f787	dev/config/fulcrum/tls.key	View secret
7593115	Elliptic Curve Private Key	86cb4de	dev/config/lnd/tls.key	View secret
7652397	Generic High Entropy Secret	de79369	.env	View secret
7652397	Generic High Entropy Secret	6c7c422	.env	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[nicolasburtey]

would it make to look into terraform so we have some parity with prod, instead of having a script? or that would not make sense for dev?

[bodymindarts]

IMO too much overhead to bring in another tool for dev.

[vindard]

Looks good to me. Local workflows work, and I can see how we might tailor this to be able to run integration/bats test against soon

[vindard]

Is the intention to eventually remove these files from core/api/dev?

[bodymindarts]

yes