-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Labels
backendRelated to the back endRelated to the back enddecision neededA decision is required (e.g. on UX or company policy)A decision is required (e.g. on UX or company policy)dependenciesPull requests that update a dependency filePull requests that update a dependency filedeveloper experience (DX)Improves our lives/efficiency as developersImproves our lives/efficiency as developerstech-debtTechnical debt (tidy up, refactoring, restructuring, caused by laziness now)Technical debt (tidy up, refactoring, restructuring, caused by laziness now)
Description
We have a CLI command octue deploy that can deploy services to Cloud Run and Dataflow. It works reasonably well although is reasonably brittle and should probably be updated to use something like terraform. It was built to use a specific version of the gcloud CLI tool. For the command to work on any system, something like Docker needs to be used to ensure the correct version of gcloud is available. This isn't ideal as a user of the SDK wouldn't just be able to run the CLI command and guarantee it would work without downloading a docker image.
Perhaps we should think about:
- Whether sers are actually going to use
octue deploy - Whether it's worth updating this tech-indebted deployment tool or if we should switch to
terraformor similar - Using some other deployment tool
Metadata
Metadata
Assignees
Labels
backendRelated to the back endRelated to the back enddecision neededA decision is required (e.g. on UX or company policy)A decision is required (e.g. on UX or company policy)dependenciesPull requests that update a dependency filePull requests that update a dependency filedeveloper experience (DX)Improves our lives/efficiency as developersImproves our lives/efficiency as developerstech-debtTechnical debt (tidy up, refactoring, restructuring, caused by laziness now)Technical debt (tidy up, refactoring, restructuring, caused by laziness now)
Type
Projects
Status
No status