Skip to content

Conversation

@jeffreyaven
Copy link
Member

Description

New features:

  • inline sql for command type resources

Other updates:

  • doc website updates
  • examples for databricks

Checklist

Please make sure that the following criteria are met:

  • The PR title is descriptive.
  • For example stacks, I have included a descriptive README.md in the example project directory, which describes the stack and includes instructions to deploy or test.
  • For example stacks, add your stack to the website template library at website/docs/template-library/.. which gets published to stackql-deploy.io (optional)
  • I have ⭐'ed the stackql and stackql-deploy repos.

Additional Notes

None.

@gitguardian
Copy link

gitguardian bot commented Jul 21, 2025

⚠️ 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
15605711 Triggered Generic High Entropy Secret 1cd440f examples/databricks/all-purpose-cluster/stackql_manifest.yml 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


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

@jeffreyaven jeffreyaven merged commit e5f12e6 into main Jul 21, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants