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

Expose csvTimeout and possibly subscriptionTimeout as Configurable ENV's #1119

Open
acornett21 opened this issue Jan 23, 2024 · 0 comments · May be fixed by #1198
Open

Expose csvTimeout and possibly subscriptionTimeout as Configurable ENV's #1119

acornett21 opened this issue Jan 23, 2024 · 0 comments · May be fixed by #1198
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@acornett21
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Recently there was an issue where a partners operator took 5-10mins on average to become healthy, but sometimes it took 2mins, and one time it took 2mins it passed the marketplace pipeline, but the certification pipeline it would always fail. This means that their operator was released in one catalog and not the other, and the CI pipeline had to be ran on their behalf to resolve the issue.

Describe the solution you'd like.

It would make sense to expose these timeouts as ENV's so that if we run into this again, we can override this in preflight-trigger and possibly the hosted pipeline as well.

Describe alternatives you've considered.

I think flags would be overkill for this, but that could be another option as well, since flags give us ENV's for free.

Additional context.

Here is more info in an ISV-ISSUE

@acornett21 acornett21 added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 23, 2024
@acornett21 acornett21 self-assigned this Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant