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

OPSEXP-2242: remove usage of lookup in alfresco-repository #105

Merged
merged 31 commits into from
Sep 8, 2023
Merged

Conversation

alxgomz
Copy link
Contributor

@alxgomz alxgomz commented Sep 5, 2023

Ref: OPSEXP-2242

Reverting as unusable when called from a parent chart

@alxgomz alxgomz requested review from gionn and slohe1 September 6, 2023 07:03
@alxgomz alxgomz changed the title OPSEXP-2043: revert usage of lookup in alfresco-repository OPSEXP-2242: revert usage of lookup in alfresco-repository Sep 6, 2023
@alxgomz alxgomz changed the title OPSEXP-2242: revert usage of lookup in alfresco-repository OPSEXP-2242: remove usage of lookup in alfresco-repository Sep 6, 2023
@@ -233,3 +239,7 @@ global:
alfrescoRegistryPullSecrets: quay-registry-secret
# -- a fallback for .Values.known_urls that can be shared between charts
known_urls:

# @ignore
Copy link
Member

Choose a reason for hiding this comment

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

it is not better to document the purpose of this? users are going to discover it anyway by looking at values

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it would just be "doc pollution" as no one is ever supposed to use that. If we end up introducing something valuable to users as tags then we would document it

Copy link
Member

Choose a reason for hiding this comment

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

users are not supposed to use that but I see a value telling them explicitly "this is just for testing the chart - don't use it"

keys:
# -- Key within the secret holding the message broker username
username: BROKER_USERNAME
# -- Key within the secret holding the message broker password
password: BROKER_PASSWORD
existingConfigMap:
# -- Name of a pre-existing configmap containing the meesage broker URL
name: null
name: ""
Copy link
Member

Choose a reason for hiding this comment

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

why?

Copy link
Contributor Author

@alxgomz alxgomz Sep 8, 2023

Choose a reason for hiding this comment

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

This is needed by the tpl() function which expects a string and breaks in case of a null object instead. But as I write this I think it would be better to cast the value when using the function to make the whole thing more robust... wdyt?

Copy link
Member

Choose a reason for hiding this comment

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

well if it's just for that it's better to handle that specific case there and do not pollute values with empty strings instead of plain nulls

Copy link
Contributor Author

Choose a reason for hiding this comment

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

reverted the whole tpl thing for now

charts/alfresco-repository/README.md Outdated Show resolved Hide resolved
charts/alfresco-repository/README.md Outdated Show resolved Hide resolved
charts/alfresco-repository/templates/_helpers-database.tpl Outdated Show resolved Hide resolved
@alxgomz alxgomz requested a review from gionn September 8, 2023 11:39
@alxgomz alxgomz merged commit d66c0fb into main Sep 8, 2023
@alxgomz alxgomz deleted the OPSEXP-2043 branch September 8, 2023 13:45
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.

2 participants