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

fix(print-platform): update dependency prefect to v2.10.21 #9790

Merged
merged 1 commit into from
Jul 13, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 13, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
prefect (source, changelog) 2.10.20 -> 2.10.21 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.


Release Notes

PrefectHQ/prefect (prefect)

v2.10.21

Compare Source

The Prefect Dashboard - your heads up display

The response to the experimental Prefect dashboard was so enthusiastic that we've made it generally availible as the default landing page in the Prefect UI. The dashboard provides an overview of all Prefect activity, surfaces the urgent information, and provides the context to understand that information. With the dashboard, you can:

  • Confirm that all flows run in the past 24 hours behaved as expected
  • Identify a flow run that recently failed and jump directly to its page
  • See a work pool that is unhealthy and the work that is impacted
Deploy deployments prefixed by flow name during prefect deploy

You can now specify the deployment to be executed by prefixing the deployment name with the flow name.

For example, the following command creates a deployment with the name my-deployment for a flow with the name my-flow:

prefect deploy --name my-flow/my-deployment

This is especially useful when you have several flows with deployments that have the same name.

For implementation details, see the following pull request:

Use environment variables in deployment steps

Prefect now supports the usage of environment variables in deployment steps, allowing you to access environment variables during the pull action at runtime or during the build and push actions when running prefect deploy. Particularly useful for CI/CD builds, this makes Prefect deployments more versatile.

For example, you can now use the following syntax to set an image tag of a Dockerized build by loading an environment variable during the build action:

build:
- prefect_docker.deployments.steps.build_docker_image:
    requires: prefect-docker>0.1.0
    image_name: my-image/orion
    tag: '{{ $CUSTOM_TAG }}'

User can also use environment variables inside of steps.

For example:

- prefect.deployments.steps.run_shell_script:
    script: echo "test-'{{ $PREFECT_API_URL }}'"
    stream_output: true

For implementation details, see the following pull request:

Use prefect deploy with multiple deployments with the same name

When there are multiple deployments with the same name, the prefect deploy command now prompts you to choose which one to deploy:

For example, if you have the following prefect.yaml:

deployments:
- name: "default"
  entrypoint: "flows/hello.py:hello"

- name: "default"
  entrypoint: "flows/hello.py:hello_parallel"

running prefect deploy -n default will now prompt you to choose which flow to create a deployment for:

prompt choose a deployment

For implementation details, see the following pull request:

Enhancements
Fixes
Documentation

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from hongbo-miao as a code owner July 13, 2023 19:21
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@renovate renovate bot temporarily deployed to test July 13, 2023 19:21 Inactive
@sonarcloud
Copy link

sonarcloud bot commented Jul 13, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@mergify mergify bot merged commit cda06d5 into main Jul 13, 2023
74 of 75 checks passed
@mergify mergify bot deleted the renovate/print-platform-prefect-2.x branch July 13, 2023 19:25
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 this pull request may close these issues.

None yet

0 participants