[Indexer] Integrate pocketdex into Tiltfile

[bryanchriswhite]

Summary

• Adds the pocketdex to the tilt environment if it has been cloned to a sibling directory as "pocketdex"

• Otherwise, if localnet_config.yaml has indexer.enabled and indexer.clone_if_not_present set to true Tilt will clone it to a sibling directory

• Otherwise a stub service titled "Indexer Disabled" under the "Pocketdex" label group explains what changes need to be made to the localnet_config.yaml:

  

Running cmd: echo 'Pocketdex indexer disabled. Set `indexer.enabled` to `true` in `localnet_config.yaml` to enable it.'
Pocketdex indexer disabled. Set `indexer.enabled` to `true` in `localnet_config.yaml` to enable it.

Running cmd: echo 'Pocketdex repo not found. Set `clone_if_not_present` to `true` in `localnet_config.yaml` to clone the repo.'
Pocketdex repo not found. Set `clone_if_not_present` to `true` in `localnet_config.yaml` to clone the repo.

Issue

• [Tooling] Integrate pocketdex into Tilt #873

Type of change

Select one or more from the following:

• New feature, functionality or library
• Consensus breaking; add the consensus-breaking label if so. See [Infra] Automatically add the consensus-breaking label #791 for details
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Testing

• Documentation: make docusaurus_start; only needed if you make doc changes
• Unit Tests: make go_develop_and_test
• LocalNet E2E Tests: make test_e2e
• DevNet E2E Tests: Add the devnet-test-e2e label to the PR.

Sanity Checklist

• I have tested my changes using the available tooling
• I have commented my code
• I have performed a self-review of my own code; both comments & source code
• I create and reference any new tickets, if applicable
• I have left TODOs throughout the codebase, if applicable

[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
12819930	Triggered	Generic Password	a24803f	localnet/kubernetes/values-pocketdex-postgres.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.}

[Olshansk]

@bryanchriswhite What will it take to make this ready for review?

[bryanchriswhite]

@Olshansk I want to check for any cleanup that needs to be done in pocketdex#23 and it needs to be merged to main before this can be merged.

[Olshansk]

@bryanchriswhite Pushed my changes after review + offline discussion in [1].

Requesting changes as a checkpoint for when you need me to take another look at this.

[1] https://discord.com/channels/824324475256438814/1296487759745253408

comments addressed

[okdas]

You've upped Tiltfile game in this repo! :D Now we're going to need to break our main huge Tiltfile into smaller ones. This is great, thank you!