Skip to content

Migrate Database Update Github action to a GCP function #260

@davidgamez

Description

@davidgamez

Describe the problem

Why should we migrate the Database Update Github action to a GCP function?

  • The Database Update Github action generates the DB models that, in certain situations, can be out of sync with the underlying code.
  • The content update can be triggered in a context different from Github actions.

Proposed solution

  • Create a GCP function based on the populate script
  • Create a queue and trigger the events from the catalog repository after a PR is mergemerged

Alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions