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

Pipeline services configuration management + deployment #6

Open
max-ostapenko opened this issue Sep 9, 2024 · 1 comment · May be fixed by #20
Open

Pipeline services configuration management + deployment #6

max-ostapenko opened this issue Sep 9, 2024 · 1 comment · May be fixed by #20

Comments

@max-ostapenko
Copy link
Contributor

max-ostapenko commented Sep 9, 2024

Apart from Dataform we have at least Cloud Scheduler + Cloud Run functions involved in managing pipelines.

All services were configured manually in the GCP console (some steps noted).
Need to remember to deploy Function by running npm run deploy after changes.

We would have a better overview and less potential failures if all these 3 services are configured from IaC within the repo and applied on main commits.

Can be implemented with Terraform and gcloud.

@max-ostapenko
Copy link
Contributor Author

max-ostapenko commented Sep 18, 2024

Added BQ permissions for Dataform as Data Editor on a dataset level (required to create SQL procedures) for each destination.

Regarding the IaC tool, I actually would favor Pulumi over Terraform here:

  • common language (JS or Python) and thus scripting capabilities (nice to use same language while working on different pipelines parts),
  • easy dependency handling (as npm package),
  • equal resources coverage.

@max-ostapenko max-ostapenko linked a pull request Oct 12, 2024 that will close this issue
6 tasks
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 a pull request may close this issue.

1 participant