We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
mysql
In addition to redis and postgres, and like in score-compose it would be great to have mysql supported in the default provisioners of score-k8s init.
redis
postgres
score-compose
score-k8s init
I know we have this disclaimer about the current small list of default provisioners, but it will greatly simplify and accelerate the adoption as mysql is a very popular use case.
Example with: https://github.com/humanitec-architecture/backstage/blob/main/templates/node-service/content/score.yaml#L36
The text was updated successfully, but these errors were encountered:
Something around this for example: https://github.com/humanitec-architecture/resource-packs-in-cluster/blob/main/humanitec-resource-defs/mysql/basic/main.tf
Sorry, something went wrong.
astromechza
Successfully merging a pull request may close this issue.
In addition to
redis
andpostgres
, and like inscore-compose
it would be great to havemysql
supported in the default provisioners ofscore-k8s init
.I know we have this disclaimer about the current small list of default provisioners, but it will greatly simplify and accelerate the adoption as
mysql
is a very popular use case.Example with: https://github.com/humanitec-architecture/backstage/blob/main/templates/node-service/content/score.yaml#L36
The text was updated successfully, but these errors were encountered: