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

feat(): Migrate sealights tasks from integration catalog to build-definitions #1868

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

flacatus
Copy link
Contributor

@flacatus flacatus commented Jan 28, 2025

I open this Pull Request to migrate the current Sealights tasks that are living currently in tekton-integration-catalog. The reason of migration is that we cannot use the tasks from catalog due to EC violations during builds. For now this migration is temporary until Konflux support https://issues.redhat.com/browse/KONFLUX-4530.

@ascerra @Dannyb48 @psturc @arewm @lcarva @konflux-ci/build-maintainers FYI

@flacatus flacatus requested a review from a team as a code owner January 28, 2025 22:11
@flacatus flacatus force-pushed the sealights branch 7 times, most recently from 38833eb to b683c35 Compare January 28, 2025 22:28
@flacatus
Copy link
Contributor Author

/retest

@mmorhun mmorhun added this pull request to the merge queue Jan 29, 2025
@@ -95,6 +95,10 @@
/stepactions/eaas-get-supported-ephemeral-cluster-versions @amisstea @avi-biton @hmariset @omeramsc @yftacherzog
/task/eaas-provision-space @amisstea @avi-biton @hmariset @omeramsc @yftacherzog

# renovate groupName=sealights
/task/sealights-go @ascerra @flacatus @psturc @dbaez
/task/sealights-python @ascerra @flacatus @psturc @dbaez
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

The names of tasks that work with trusted artifacts have -oci-ta in the name, consider renaming for consistency.

Is there no need to have regular, non -trusted-artifacts versions of these tasks?

PACKAGES_EXCLUDED_ENUM="$(IFS=,; printf "%s," "$@" | sed 's/,$//')"

wget -qO- https://agents.sealights.co/slgoagent/latest/slgoagent-linux-amd64.tar.gz | tar -xzv -C /usr/local/bin
wget -qO- https://agents.sealights.co/slcli/latest/slcli-linux-amd64.tar.gz | tar -xzv -C /usr/local/bin
Copy link
Contributor

Choose a reason for hiding this comment

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

Downloading a binary at runtime doesn't seem very secure. Do you have plans to build a container image with the sealights binaries?

EXCLUDE_ENUM="$(IFS=,; printf "%s," "$@" | sed 's/,$//')"

# Installs Sealights Python agent.
pip install sealights-python-agent
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here, installing an unspecified version at runtime is not great

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