feat: optionally bypass runtime dependency checks [sc-22475] #986
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces a new option called `--[no-]verify-runtime-dependencies` for the test and deploy commands, which is true by default and matches current behavior. Should the user decide that they know the available dependencies better than we do, they can run the commands with the `--no-verify-runtime-dependencies` flag set, or they can use the equivalent `CHECKLY_VERIFY_RUNTIME_DEPENDENCIES=0` environment variable. Specifically, this feature makes it possible to use custom dependencies that have been added to a customized private location runtime (contact your Account Executive to learn how).
Makes it easier to use parseProject in tests.
sorccu
changed the title
clample
approved these changes
Nov 29, 2024
sorccu
deleted the
simokinnunen/sc-22475/let-user-optionally-bypass-allowed-dependency
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces a new option called
--[no-]verify-runtime-dependenciesfor thetestanddeploycommands, which istrueby default and matches current behavior. Should the user decide that they know the available dependencies better than we do, they can run the commands with the--no-verify-runtime-dependenciesflag set, or they can use the equivalentCHECKLY_VERIFY_RUNTIME_DEPENDENCIES=0environment variable.Specifically, this feature makes it possible to use custom dependencies that have been added to a customized private location runtime (contact your Account Executive to learn how).
I hereby confirm that I followed the code guidelines found at engineering guidelines
Affected Components
Notes for the Reviewer
New Dependency Submission