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

chore(pipeline-backend): add artifact config for pipeline-backend #1153

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

chuang8511
Copy link
Contributor

Because

  • we need the env var

This commit

  • add config

Copy link

linear bot commented Nov 12, 2024

@chuang8511 chuang8511 changed the title chore: add artifact config for pipeline-backend chore(pipeline-backend): add artifact config for pipeline-backend Nov 12, 2024
@chuang8511
Copy link
Contributor Author

Not sure how to set this env var in terraform. Will need to confirm if it is set already.

…ateway

chore(pipeline-backend): update config for api gateway in configmap
@chuang8511 chuang8511 force-pushed the chunhao/ins-6780-pipeline-artifact-setting branch from 41118cc to bc66a52 Compare November 14, 2024 13:55
@@ -117,3 +118,6 @@ data:
rootpwd: {{ .Values.pipelineBackend.minio.rootpwd }}
bucketname: {{ .Values.pipelineBackend.minio.bucketname }}
secure: {{ .Values.pipelineBackend.minio.secure }}
apigateway:
host: {{ template "core.apiGateway" . }}
publicport: {{ template "core.apiGateway.httpPort" . }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Need to check if the terraform has set it.

@chuang8511 chuang8511 marked this pull request as ready for review November 14, 2024 16:57
@donch1989 donch1989 merged commit ef82953 into main Nov 18, 2024
13 checks passed
@donch1989 donch1989 deleted the chunhao/ins-6780-pipeline-artifact-setting branch November 18, 2024 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: No status
Development

Successfully merging this pull request may close these issues.

3 participants