You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users when forking our repo, would like to have the power to skip the cloud tests when they are not required, we could use the same idea that @tylergraff suggested on #2369
I prose we collapse all testing into a single yaml file, where we can keep it running on schedule and also add and extra conditional check as the one proposed on the above issue, so that it can be skipped. The main reason to collapse it would be that most of the current logic is mostly the same
Value and/or benefit
help devex when forking the repo
better control over the current tests
Anything else?
No response
The text was updated successfully, but these errors were encountered:
I support the idea of having one yaml file that handles cloud providers deployment—at the end the logic behind deploying is the same and the only thing that changes are configuration options and credentials. What I think we could do is abstract the logic into a reusable workflow that we then call multiple times, once for each provider.
Feature description
Some users when forking our repo, would like to have the power to skip the cloud tests when they are not required, we could use the same idea that @tylergraff suggested on #2369
I prose we collapse all testing into a single yaml file, where we can keep it running on schedule and also add and extra conditional check as the one proposed on the above issue, so that it can be skipped. The main reason to collapse it would be that most of the current logic is mostly the same
Value and/or benefit
Anything else?
No response
The text was updated successfully, but these errors were encountered: