-
Notifications
You must be signed in to change notification settings - Fork 124
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
Minimum permissions required on Service account #21
Comments
@Mike-Dunton We don't have cycles to do this but would welcome community contributions for it! FWIW most the providers use only a few API calls to read metadata etc. |
Ill see about getting this together. Thanks for the ping. |
it's frustrating to hear this because we already had some of this in place for azure testing I contributed to - and it's since been removed from this project 😞 |
@flyinprogrammer interesting I’m not aware of the removal of this specifically, though we did make several changes to try and ensure we could automatically verify this in CI so maybe we removed it in the process? Do you mind pointing out what you added that covered this so I can look in the git history? Definitely been great to get of all your contributions here, it’s helped substantially! |
15f16c2#diff-4c440ab944dc623279154e7a371f5292 it's all good - it seems the azure stuff is once again on 🔥so i'll have some prs with a readme soon enough. i have a vested interest in the gcp and aws providers as well. so documenting their minimum requirements shouldn't be too hard. i'll make sure to submit a PR to the consul documentation as well since it's effectively useless atm when it comes to the azure stuff, which is entirely my fault. ❤️ it's all gonna be ok. I understand the changes you guys needed to make, i think the current CI process is much simpler for folks. |
Could we get an updated readme that lays out the required permissions for each provider.
I am looking at what level of permissions are needed on the service account to use the GCE provider.
The text was updated successfully, but these errors were encountered: