Skip to content

Conversation

@bromiesTM
Copy link
Contributor

No description provided.

@bromiesTM bromiesTM force-pushed the kh/dev/configure-richdocuments branch 3 times, most recently from ad02695 to f3add9d Compare April 1, 2025 07:43
@bromiesTM bromiesTM force-pushed the kh/dev/configure-richdocuments branch from f3add9d to ddce08a Compare April 2, 2025 07:13
@bromiesTM bromiesTM requested a review from printminion-co April 9, 2025 09:25
@printminion-co printminion-co force-pushed the kh/dev/configure-richdocuments branch from 3470c52 to 0d20ca5 Compare April 9, 2025 13:51
Copy link
Contributor

@printminion-co printminion-co left a comment

Choose a reason for hiding this comment

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

review ok if amends are accepted

  • lets move richdocuments disable/enable logic to configure.sh.
  • lets ensure yes/no values is used for disable_certificate_verification because COLLABORA_SELF_SIGNED env is set to boolean via helm

@bromiesTM bromiesTM force-pushed the kh/dev/configure-richdocuments branch from d7f6b61 to 1ac0ef9 Compare April 10, 2025 06:40
@printminion-co printminion-co merged commit 1f309bc into master Apr 10, 2025
1 check passed
@printminion-co printminion-co deleted the kh/dev/configure-richdocuments branch April 10, 2025 07:52
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