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

LOPS-2300 - Create Terminus Wait for Commit command #2585

Closed

Conversation

stovak
Copy link
Member

@stovak stovak commented May 16, 2024

This PR creates a new command based on the new workflow Logs API and will move the main workflow functions to the new Workflow API in an effort to allow customers to wait for a specific commit to be deployed.

@stovak stovak requested a review from a team as a code owner May 16, 2024 23:11
Copy link

guardrails bot commented May 23, 2024

⚠️ We detected 1 security issue in this pull request:

Insecure File Management (1)
Severity Details Docs
Medium Title: Remote File Inclusion with user input
include_once(getenv('PROJECT_PATH') . '/vendor/autoload.php');
📚

More info on how to fix Insecure File Management in PHP.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

Building out collections and find logic

linting

Linting

Adding documentation

The Waiting
@stovak stovak force-pushed the LOPS-2300-Create-Terminus-Workflow-waitForCommit-command branch from ea16b8b to 847f77e Compare May 23, 2024 23:58
* @aliases workflows
*
* @option bool $all Return all of the available workflows, not just the most recent 100
* @option bool $all Requests are limited to the last 10 workflows run. This option has been deprecated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the option has been deprecated? why?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I go by the updated description this is a breaking change that should not be taken lightly. We recently got a ticket (BUGS?) for a customer that wasn't happy getting only 100 workflows and wanted them all; now having only 10 will make them (and lots of other customers I guess) very unhappy

@stovak stovak closed this May 29, 2024
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

3 participants