-
Notifications
You must be signed in to change notification settings - Fork 1
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
Things to do for release #1
Comments
Optional, but it might be useful for users if the docs have some example of outputs. Will be helpful to know what the outputs and PR comments would look like. |
From what I gather from looking at the code, seems like this supports multiple directories right? |
The python code does support it, but the action itself doesn't support it since the input cannot be a list of string. (yet) Since there's a possibility that different directories require different terraform version, I prefer to have this action called per-directory. |
Oh, I guess it might work if the input is |
Yeah, it works using multiline input actions/toolkit#184 (comment) For terraform version, we could have similar multiple input for it as well. Setting just 1 will make all directories use the same version. Setting nothing is the same as setting 1 with |
Although will need more implementation to support the different terraform versions 😅 |
Yeah, supporting different terraform version is more complicated as github workflow doesn't support looping ... I'd like to have the python code to be usable locally as well, so putting terraform setup inside it might cause conflicts when run locally. |
Or maybe we can use tfenv instead of setup-terraform |
yes, just about to mention that. can use something like this https://github.com/rhythmictech/actions-setup-tfenv |
Is there anything else I need to make sure before making this repo public?
I tested this in a rather roundabout way since Github Actions couldn't directly use action from a private repo:
https://github.com/HENNGE/shobo-support-viewer/pull/217
The text was updated successfully, but these errors were encountered: