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

fixes #215 and allows customconfigs deployments in puppetdb #227

Merged

Conversation

anthonysomerset
Copy link
Contributor

fixes #215 and allows customconfigs deployments in puppetdb by removing the duplicate volume mount block

@Xtigyro
Copy link
Contributor

Xtigyro commented May 7, 2024

@anthonysomerset Would you mind please how your code is then sourced?

This one:

puppetdb:
  tag: 7.18.0-v1.5.0
  extraEnv:
    PUPPETDB_POSTGRES_HOSTNAME: dbhostname.postgres.database.azure.com
  customconfigs:
    enabled: true
    configmaps:
      database.conf: |-
        database: {
          subname: "//"${PUPPETDB_POSTGRES_HOSTNAME}":"${PUPPETDB_POSTGRES_PORT}"/"${PUPPETDB_POSTGRES_DATABASE}
          username: ${PUPPETDB_USER}
          password: ${PUPPETDB_PASSWORD}
          node-ttl: ${PUPPETDB_NODE_TTL}
          node-purge-ttl: ${PUPPETDB_NODE_PURGE_TTL}
          report-ttl: ${PUPPETDB_REPORT_TTL}
          facts-blocklist: ".*veth.*"
          facts-blocklist-type: regex
        }

@anthonysomerset
Copy link
Contributor Author

this is basically an example reference values.yaml that i used for testing and validation that the deployment works

the extraEnv for the db hostname was to respond to the referenced issue where the user needed to use an external DB and thus customconfigs is NOT required in their case anyway

the custom config was my example and use case of setting a facts-blocklist as a valid customconfig that did need such (and now works)

is that what you were looking for?

@Xtigyro
Copy link
Contributor

Xtigyro commented May 8, 2024

@anthonysomerset Sorry, I am probably missing something but aren't you eliminating here the possibility the above to be sourced?

@anthonysomerset
Copy link
Contributor Author

no - it now works without generating an error as in #215

The configmap is an example to override database.conf, all but the last 2 lines are default config i am replaying for safety sake - might not be needed but haven't verified further either at this stage

@Xtigyro
Copy link
Contributor

Xtigyro commented May 8, 2024

@anthonysomerset Thank you!

I believe it would be very nice if you become part of the official maintainers - so please feel free to send a PR and add yourself. Should be here, here, and here. When we do that, I'll ask the puppetlabs GitHub owners to give you write access to this repo.

@Xtigyro Xtigyro merged commit 0bcd6d9 into puppetlabs:master May 8, 2024
3 checks passed
@anthonysomerset anthonysomerset deleted the puppetdb_custom_configmap_fix branch May 9, 2024 05:22
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.

Invalid Puppet DB Deployment
2 participants