Skip to content

Add default postgres-instance provisioner#284

Merged
chris-stephenson merged 5 commits intoscore-spec:mainfrom
rabelmervin:main
Apr 15, 2025
Merged

Add default postgres-instance provisioner#284
chris-stephenson merged 5 commits intoscore-spec:mainfrom
rabelmervin:main

Conversation

@rabelmervin
Copy link
Copy Markdown
Contributor

Description

A new provisioner, postgres-instance, has been added. It is similar to the postgres provisioner but differs in key aspects:

  • Unlike the postgres provisioner, postgres-instance does not provide database/name as an output.

  • It operates without shared resources (local )

Signed-off-by: rabelmervin <rabelmervin@gmail.com>
Signed-off-by: rabelmervin <rabelmervin@gmail.com>
@rabelmervin
Copy link
Copy Markdown
Contributor Author

rabelmervin commented Apr 1, 2025

Bonjour Monsieur, @mathieu-benoit, sorry for the previous pr. Now its look cleaner and updated...

@mathieu-benoit mathieu-benoit self-requested a review April 4, 2025 14:44
Copy link
Copy Markdown
Contributor

@chris-stephenson chris-stephenson left a comment

Choose a reason for hiding this comment

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

Thanks for taking the time to submit the PR @rabelmervin ! We really appreciate the support.

I left a few comments - but this might be more related to me not fully understanding your usecase.

In your description you worte:

  • Unlike the postgres provisioner, postgres-instance does not provide database/name as an output.

  • It operates without shared resources (local )

The first one makes sense, but I don't understand you mean regarding the second point.

I assume that you want to allow a workload to have admin on the Postgres instance itself (a good example of this might be wanting to run backstage with score for example)

In this case there are a few things to consider:

  1. Should the postgres instance be the same as the one used by the postgres type?
  2. How much of the original postgres provisioner would actually be required.

Feel free to follow up with questions or reach out on the CNCF slack if you have further questions.

Signed-off-by: rabelmervin <rabelmervin@gmail.com>
@rabelmervin
Copy link
Copy Markdown
Contributor Author

Hi @chris-stephenson Apologies for pushing the previous commit without properly addressing the issue. Thanks for your review

Signed-off-by: rabelmervin <rabelmervin@gmail.com>
Copy link
Copy Markdown
Contributor

@chris-stephenson chris-stephenson left a comment

Choose a reason for hiding this comment

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

Almost there! Thanks for putting the time in. :)

Signed-off-by: rabelmervin <rabelmervin@gmail.com>
Copy link
Copy Markdown
Contributor

@chris-stephenson chris-stephenson left a comment

Choose a reason for hiding this comment

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

LGTM

@chris-stephenson chris-stephenson merged commit ca57be6 into score-spec:main Apr 15, 2025
6 checks passed
@mathieu-benoit mathieu-benoit changed the title Postgres-instance provisioner added Add default postgres-instance provisioner Jun 3, 2025
@mathieu-benoit
Copy link
Copy Markdown
Contributor

Thanks @rabelmervin for this implementation, and thanks @chris-stephenson for the review, this is helping making this entire use case with Backstage working now! 🎉
https://medium.com/@mabenoit/deploy-backstage-with-score-45bb2d7c2d90.

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.

[feature request] add postgres-instance provisioner based on postgres provisioner

3 participants