Enable tag-based deployment for dbt-metricflow #1349
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to be able to start deploying dbt-metricflow via tags that trigger a deployment action instead of relying on manual deployment. This is necessary for two reasons: 1. The MetricFlow repository is evolving to allow for multiple package deployments in distinctive ways, and each package would benefit from a set of pre-deployment steps. 2. With the CLI now bundled with dbt-metricflow we need a structured way of adding and deploying patch fixes for versions that are too far behind the current repo main branch to deploy off of main. Therefore, this PR splits our PyPI deployment action into two separate versions with different tag-format triggers, one for MetricFlow and the other for dbt-metricflow. Authentication for dbt-metricflow will be managed via PyPI's Trusted Publisher mechanism. MetricFlow will follow suit once the relevant PyPI enrollments are ready. Note these are separate files with some duplication here, but it's minimal, and we expect further divergence over time as we develop package-specific pre-deployment tests for these packages.
courtneyholcomb
approved these changes
Jul 25, 2024
tlento
added a commit
that referenced
this pull request
Jul 27, 2024
We need to be able to start deploying dbt-metricflow via tags that trigger a deployment action instead of relying on manual deployment. This is necessary for two reasons: 1. The MetricFlow repository is evolving to allow for multiple package deployments in distinctive ways, and each package would benefit from a set of pre-deployment steps. 2. With the CLI now bundled with dbt-metricflow we need a structured way of adding and deploying patch fixes for versions that are too far behind the current repo main branch to deploy off of main. Therefore, this PR splits our PyPI deployment action into two separate versions with different tag-format triggers, one for MetricFlow and the other for dbt-metricflow. Authentication for dbt-metricflow will be managed via PyPI's Trusted Publisher mechanism. MetricFlow will follow suit once the relevant PyPI enrollments are ready. Note these are separate files with some duplication here, but it's minimal, and we expect further divergence over time as we develop package-specific pre-deployment tests for these packages.
tlento
added a commit
that referenced
this pull request
Jul 30, 2024
We need to be able to start deploying dbt-metricflow via tags that trigger a deployment action instead of relying on manual deployment. This is necessary for two reasons: 1. The MetricFlow repository is evolving to allow for multiple package deployments in distinctive ways, and each package would benefit from a set of pre-deployment steps. 2. With the CLI now bundled with dbt-metricflow we need a structured way of adding and deploying patch fixes for versions that are too far behind the current repo main branch to deploy off of main. Therefore, this PR splits our PyPI deployment action into two separate versions with different tag-format triggers, one for MetricFlow and the other for dbt-metricflow. Authentication for dbt-metricflow will be managed via PyPI's Trusted Publisher mechanism. MetricFlow will follow suit once the relevant PyPI enrollments are ready. Note these are separate files with some duplication here, but it's minimal, and we expect further divergence over time as we develop package-specific pre-deployment tests for these packages.
tlento
added a commit
that referenced
this pull request
Jul 30, 2024
#1362) Backport of three PRs required to enable tag-based deployment from the `support/dbt-metricflow-0.7.x` branch. Specifically: - **Enable tag-based deployment for dbt-metricflow (#1349)** - **Remove access token reference for PyPI (#1350)** - **Enable Trusted Publishing for PyPI actions (#1356)**
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to be able to start deploying dbt-metricflow via tags that
trigger a deployment action instead of relying on manual deployment.
This is necessary for two reasons:
package deployments in distinctive ways, and each package would benefit
from a set of pre-deployment steps.
of adding and deploying patch fixes for versions that are too far
behind the current repo main branch to deploy off of main.
Therefore, this PR splits our PyPI deployment action into two separate
versions with different tag-format triggers, one for MetricFlow and
the other for dbt-metricflow. Authentication for dbt-metricflow will
be managed via PyPI's Trusted Publisher mechanism. MetricFlow will
follow suit once the relevant PyPI enrollments are ready.
Note these are separate files with some duplication here, but it's minimal,
and we expect further divergence over time as we develop package-specific
pre-deployment tests for these packages.