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

Bump integrations to 0.10.11 and improve fake integration #1025

Merged
merged 6 commits into from
Sep 17, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -89,3 +89,4 @@ jobs:
report_paths: '**/junit/test-results-**/*.xml'
include_passed: true
require_tests: true
fail_on_failure: true
58 changes: 14 additions & 44 deletions integrations/_infra/Dockerfile
Original file line number Diff line number Diff line change
@@ -1,58 +1,28 @@
FROM python:3.11-alpine AS base
FROM python:3.11-slim-bookworm

ARG BUILD_CONTEXT

ENV LIBRDKAFKA_VERSION=1.9.2

# Install system dependencies and libraries
RUN apk add --no-cache \
gcc \
musl-dev \
build-base \
bash \
oniguruma-dev \
make \
autoconf \
automake \
libtool \
curl \
libffi-dev && \
echo "@edge http://dl-cdn.alpinelinux.org/alpine/edge/main" >> /etc/apk/repositories \
&& echo "@edgecommunity http://dl-cdn.alpinelinux.org/alpine/edge/community" >> /etc/apk/repositories \
&& apk add --no-cache alpine-sdk "librdkafka@edgecommunity>=${LIBRDKAFKA_VERSION}" "librdkafka-dev@edgecommunity>=${LIBRDKAFKA_VERSION}" && curl -sSL https://install.python-poetry.org | python3 - \
&& /root/.local/bin/poetry config virtualenvs.in-project true

WORKDIR /app

COPY ./${BUILD_CONTEXT}/pyproject.toml ./${BUILD_CONTEXT}/poetry.lock /app/

RUN /root/.local/bin/poetry install --without dev --no-root --no-interaction --no-ansi --no-cache && pip cache purge

FROM python:3.11-alpine AS prod

ARG INTEGRATION_VERSION
ARG BUILD_CONTEXT

LABEL INTEGRATION_VERSION=${INTEGRATION_VERSION}
# Used to ensure that new integrations will be public, see https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility
LABEL org.opencontainers.image.source=https://github.com/port-labs/ocean
LABEL org.opencontainers.image.source https://github.com/port-labs/ocean

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/snyk/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/datadog/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/argocd/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/azure/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/azure-devops/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/dynatrace/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/aws/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/jira/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/gitlab/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/linear/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/gcp/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/opencost/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/firehydrant/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/launchdarkly/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/jenkins/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/kubecost/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/newrelic/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/octopus/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/pagerduty/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/fake-integration/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/statuspage/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/sentry/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/sonarqube/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/opsgenie/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/kafka/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/terraform-cloud/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/wiz/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 8 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/servicenow/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

# Install only runtime dependencies
RUN apk add --no-cache \
librdkafka-dev \
bash \
oniguruma-dev
ENV LIBRDKAFKA_VERSION 1.9.2

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/snyk/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/datadog/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/argocd/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/azure/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/azure-devops/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/dynatrace/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/aws/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/jira/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/gitlab/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/linear/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/gcp/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/opencost/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/firehydrant/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/launchdarkly/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/jenkins/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/kubecost/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/newrelic/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/octopus/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/pagerduty/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/fake-integration/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/statuspage/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/sentry/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/sonarqube/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/opsgenie/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/kafka/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/terraform-cloud/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/wiz/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/servicenow/.port/spec.yaml)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

WORKDIR /app

# Copy dependencies from the build stage
COPY --from=base /app /app
RUN apt update && \
apt install -y wget make g++ libssl-dev autoconf automake libtool curl librdkafka-dev && \
apt-get clean

COPY ./integrations/_infra/init.sh /app/init.sh

RUN chmod +x /app/init.sh

# Copy the application code
COPY ./${BUILD_CONTEXT} /app

# Clean up old setuptools + update certificates if needed
RUN pip uninstall -y setuptools || true && test -e /usr/local/share/ca-certificates/cert.crt && update-ca-certificates || true
COPY ./integrations/_infra/Makefile /app/Makefile

RUN export POETRY_VIRTUALENVS_CREATE=false && make install/prod && pip cache purge

# Run the application
CMD ["/app/.venv/bin/python", "/app/.venv/bin/ocean", "sail"]
ENTRYPOINT ./init.sh

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/snyk/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/datadog/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/argocd/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/azure/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/azure-devops/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/dynatrace/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/aws/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/jira/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/gitlab/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/linear/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/gcp/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/opencost/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/firehydrant/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/launchdarkly/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/jenkins/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/kubecost/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/newrelic/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/octopus/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/pagerduty/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/fake-integration/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/statuspage/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/sentry/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/sonarqube/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/opsgenie/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/kafka/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/terraform-cloud/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/wiz/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 28 in integrations/_infra/Dockerfile

View workflow job for this annotation

GitHub Actions / build-integration (integrations/servicenow/.port/spec.yaml)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
5 changes: 5 additions & 0 deletions integrations/_infra/init.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
if test -e /usr/local/share/ca-certificates/cert.crt; then
update-ca-certificates
fi

ocean sail
8 changes: 8 additions & 0 deletions integrations/argocd/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

<!-- towncrier release notes start -->

## 0.1.87 (2024-09-17)


### Improvements

- Bumped ocean version to ^0.10.11


## 0.1.86 (2024-09-12)


Expand Down
8 changes: 4 additions & 4 deletions integrations/argocd/poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions integrations/argocd/pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
[tool.poetry]
name = "argocd"
version = "0.1.86"
version = "0.1.87"
description = "Argo CD integration powered by Ocean"
authors = ["Isaac Coffie <isaac@getport.io>"]

[tool.poetry.dependencies]
python = "^3.11"
port_ocean = {version = "^0.10.10", extras = ["cli"]}
port_ocean = {version = "^0.10.11", extras = ["cli"]}

[tool.poetry.group.dev.dependencies]
# Uncomment this if you want to debug the ocean core together with your integration
Expand Down
8 changes: 8 additions & 0 deletions integrations/aws/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

<!-- towncrier release notes start -->

## 0.2.40 (2024-09-17)


### Improvements

- Bumped ocean version to ^0.10.11


## 0.2.39 (2024-09-12)


Expand Down
8 changes: 4 additions & 4 deletions integrations/aws/poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions integrations/aws/pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
[tool.poetry]
name = "aws"
version = "0.2.39"
version = "0.2.40"
description = "This integration will map all your resources in all the available accounts to your Port entities"
authors = ["Shalev Avhar <shalev@getport.io>", "Erik Zaadi <erik@getport.io>"]

[tool.poetry.dependencies]
python = "^3.11"
port_ocean = {version = "^0.10.10", extras = ["cli"]}
port_ocean = {version = "^0.10.11", extras = ["cli"]}
python-dotenv = "^1.0.1"
aioboto3 = "^12.4.0"
boto3-stubs = {version = "1.34.76", extras = ["acm", "apigateway", "appconfig", "athena", "cloudcontrol", "cloudformation", "cloudwatch", "dynamodb", "ec2", "ec2-instance-connect", "ecr", "ecs", "elasticache", "elb", "elbv2", "events", "iam", "lambda", "logs", "organizations", "rds", "route53", "s3", "sagemaker", "secretsmanager", "sns", "sqs", "ssm", "sts"]}
Expand Down
8 changes: 8 additions & 0 deletions integrations/azure-devops/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

<!-- towncrier release notes start -->

## 0.1.68 (2024-09-17)


### Improvements

- Bumped ocean version to ^0.10.11


## 0.1.67 (2024-09-12)


Expand Down
8 changes: 4 additions & 4 deletions integrations/azure-devops/poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions integrations/azure-devops/pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
[tool.poetry]
name = "azure-devops"
version = "0.1.67"
version = "0.1.68"
description = "An Azure Devops Ocean integration"
authors = ["Matan Geva <matang@getport.io>"]

[tool.poetry.dependencies]
python = "^3.11"
port_ocean = {version = "^0.10.10", extras = ["cli"]}
port_ocean = {version = "^0.10.11", extras = ["cli"]}

[tool.poetry.group.dev.dependencies]
# Uncomment this if you want to debug the ocean core together with your integration
Expand Down
7 changes: 7 additions & 0 deletions integrations/azure/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,10 @@
0.1.91 (2024-09-17)

### Improvements

- Bumped ocean version to ^0.10.11


0.1.90 (2024-09-12)

### Improvements
Expand Down
8 changes: 4 additions & 4 deletions integrations/azure/poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions integrations/azure/pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
[tool.poetry]
name = "azure"
version = "0.1.90"
version = "0.1.91"
description = "Azure integration"
authors = ["Tom Tankilevitch <tom@getport.io>"]

[tool.poetry.dependencies]
python = "^3.11"
port_ocean = {version = "^0.10.10", extras = ["cli"]}
port_ocean = {version = "^0.10.11", extras = ["cli"]}
# due to patching the azure-mgmt-resource package, we need to use a specific version
azure-mgmt-resource = "23.0.1"
azure-identity = "^1.13.0"
Expand Down
8 changes: 8 additions & 0 deletions integrations/datadog/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

<!-- towncrier release notes start -->

## 0.1.41 (2024-09-17)


### Improvements

- Bumped ocean version to ^0.10.11


## 0.1.40 (2024-09-12)


Expand Down
8 changes: 4 additions & 4 deletions integrations/datadog/poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions integrations/datadog/pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
[tool.poetry]
name = "datadog"
version = "0.1.40"
version = "0.1.41"
description = "Datadog Ocean Integration"
authors = ["Albert Luganga <albertluganga@getport.io>"]

[tool.poetry.dependencies]
python = "^3.11"
port_ocean = {version = "^0.10.10", extras = ["cli"]}
port_ocean = {version = "^0.10.11", extras = ["cli"]}
loguru = "^0.7.2"

[tool.poetry.group.dev.dependencies]
Expand Down
8 changes: 8 additions & 0 deletions integrations/dynatrace/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

<!-- towncrier release notes start -->

## 0.1.53 (2024-09-17)


### Improvements

- Bumped ocean version to ^0.10.11


## 0.1.52 (2024-09-12)


Expand Down
8 changes: 4 additions & 4 deletions integrations/dynatrace/poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions integrations/dynatrace/pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
[tool.poetry]
name = "dynatrace"
version = "0.1.52"
version = "0.1.53"
description = "An integration used to import Dynatrace resources into Port"
authors = ["Ayodeji Adeoti <<ayodeji.adeoti@getport.io>>"]

[tool.poetry.dependencies]
python = "^3.11"
port_ocean = {version = "^0.10.10", extras = ["cli"]}
port_ocean = {version = "^0.10.11", extras = ["cli"]}

[tool.poetry.group.dev.dependencies]
# uncomment this if you want to debug the ocean core together with your integration
Expand Down
Loading
Loading