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.
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
Bump integrations to 0.10.11 and improve fake integration #1025
Bump integrations to 0.10.11 and improve fake integration #1025
Changes from all commits
756b93d
b6840d7
b3bf4e0
fb271c5
aade68f
858555e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/snyk/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/datadog/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/argocd/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/azure/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/azure-devops/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/dynatrace/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/aws/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/jira/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/gitlab/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/linear/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/gcp/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/opencost/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/firehydrant/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/launchdarkly/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/jenkins/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/kubecost/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/newrelic/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/octopus/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/pagerduty/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/fake-integration/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/statuspage/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/sentry/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/sonarqube/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/opsgenie/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/kafka/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/terraform-cloud/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/wiz/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 8 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/servicenow/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/snyk/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/datadog/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/argocd/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/azure/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/azure-devops/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/dynatrace/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/aws/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/jira/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/gitlab/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/linear/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/gcp/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/opencost/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/firehydrant/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/launchdarkly/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/jenkins/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/kubecost/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/newrelic/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/octopus/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/pagerduty/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/fake-integration/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/statuspage/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/sentry/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/sonarqube/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/opsgenie/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/kafka/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/terraform-cloud/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/wiz/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 10 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/servicenow/.port/spec.yaml)
Legacy key/value format with whitespace separator should not be used
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/snyk/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/datadog/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/argocd/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/azure/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/azure-devops/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/dynatrace/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/aws/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/jira/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/gitlab/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/linear/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/gcp/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/opencost/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/firehydrant/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/launchdarkly/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/jenkins/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/kubecost/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/newrelic/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/octopus/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/pagerduty/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/fake-integration/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/statuspage/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/sentry/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/sonarqube/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/opsgenie/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/kafka/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/terraform-cloud/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/wiz/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Check warning on line 28 in integrations/_infra/Dockerfile
GitHub Actions / build-integration (integrations/servicenow/.port/spec.yaml)
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.