Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add postman examples for Cortex inference API #8

Conversation

sfc-gh-bprosnitz
Copy link
Contributor

@sfc-gh-bprosnitz sfc-gh-bprosnitz commented Aug 6, 2024

Overview

SNOW-1538588

This PR adds some postman examples for the cortex inference API. Hoping it will make it easier for customers to understand how to use the API.

Pre-review checklist

  • I attest that this change meets the bar for low risk without security requirements as defined in the Accelerated Risk Assessment Criteria and I have taken the Risk Assessment Training in Workday.
    • Checking this checkbox is mandatory if using the Accelerated Risk Assessment to risk assess the changes in this Pull Request.
    • If this change does not meet the bar for low risk without security requirements (as confirmed by the peer reviewers of this pull request) then a formal Risk Assessment must be completed. Please note that a formal Risk Assessment will require you to spend extra time performing a security review for this change. Please account for this extra time earlier rather than later to avoid unnecessary delays in the release process.
  • This change has passed precommit
  • This change is TEST-ONLY
  • This change has been through a design review process and the test plan is signed off by the owner
  • This change is parameter protected
  • This change has code coverage for the new code added

Copy link

gitguardian bot commented Aug 6, 2024

⚠️ GitGuardian has uncovered 2 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic High Entropy Secret 5cfae99 private-preview/8.12/collection/Snowflake Cortex Inference API.postman_collection.json View secret
- - Generic High Entropy Secret 19ea7a0 private-preview/8.12/collection/Snowflake Cortex Inference API.postman_collection.json View secret
🛠 Guidelines to remediate hardcoded secrets

The above secret(s) have been detected in your PR. Please take an appropriate action for each secret:

  • If it’s a true positive, remove the secret from source code, revoke it and migrate to a secure way of storing and accessing secrets (see http://go/secrets-and-code). Once that’s done, go to the incidents page linked in the “GitGuardian id” column (log in using SnowBiz Okta) and resolve the incident.
  • If it’s a false positive, go to the incidents page linked in the “GitGuardian id” column (log in using SnowBiz Okta) and ignore the incident.
  • If you didn't add this secret - and only then - you may ignore this check as it's non-blocking. If you did add the secret and you ignore this check, you'll be assigned a "Security Finding" ticket in Jira in a few days.

Note:

  • A secret is considered leaked from the moment it touches GitHub. Rewriting git history by force pushing or other means is not necessary and doesn’t change the fact that the secret has to be revoked.
  • This check has a “Skip: false positive” button. Don’t use it. It will mark all detected secrets as false positives but only in the context of this specific run - it won’t remember this action in subsequent check runs.

If you encounter any problems you can reach out to us on Slack: #gitguardian-secret-scanning-help


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

Copy link
Contributor

@sfc-gh-igarish sfc-gh-igarish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sfc-gh-zli sfc-gh-zli merged commit e6b06c5 into snowflakedb:main Aug 9, 2024
2 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.

3 participants