Skip to content

fix(trino): correctly take the security variables for OPAL into account#3

Open
SteBaum wants to merge 2 commits into
OKDP:mainfrom
SteBaum:fix/opal-secure
Open

fix(trino): correctly take the security variables for OPAL into account#3
SteBaum wants to merge 2 commits into
OKDP:mainfrom
SteBaum:fix/opal-secure

Conversation

@SteBaum
Copy link
Copy Markdown

@SteBaum SteBaum commented May 29, 2026

Description

Related Issue

Fixes #2

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor / chore
  • Breaking change

How to Test

Checklist

  • I have tested my changes
  • Documentation updated if needed
  • If breaking change: migration path described above
  • I hereby declare this contribution to be licensed under the Apache License Version 2.0.
  • I hereby agree to grant TOSIT a copyright license to use my contributions.

@SteBaum SteBaum force-pushed the fix/opal-secure branch from e50ad31 to d88d5bc Compare May 29, 2026 12:19
@SteBaum SteBaum force-pushed the fix/opal-secure branch from d88d5bc to 344dc35 Compare May 29, 2026 12:38
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.

OPAL is not in secure mode

1 participant