We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
The pipeline should include an executable outside of the eksctl package that:
This need not be complicated, nor even connect to an actual EKS instance.
This is an example.
https://github.com/tendervittles/bad-eksctl
I have hit #8090 and #8284 when trying to import eksctl.
Both could have been easily detect before release by building an outside executable against this project.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Sorry, something went wrong.
Not stale.
No branches or pull requests
What feature/behavior/change do you want?
The pipeline should include an executable outside of the eksctl package that:
This need not be complicated, nor even connect to an actual EKS instance.
This is an example.
https://github.com/tendervittles/bad-eksctl
Why do you want this feature?
I have hit #8090 and #8284 when trying to import eksctl.
Both could have been easily detect before release by building an outside executable against this project.
The text was updated successfully, but these errors were encountered: