-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Fix/default values #10
Conversation
…nced * Fix shiled typos
…nced * Fix shiled typos
@Makeshift @dylanbannon we checked form side but we are not clear about what permission is needed by This the error in your cicd pipeline:
We introduced several fixes to make the module usable for all fms services, and would like to contribute by sharing those fixes with the community. We will be more than pleased if you guide us to merge those changes into your module. |
This pull request is now in conflict. Could you fix it @lgallard? 🙏 |
* update logging configuration to use json functions (keeps same type of string) and use null not empty brace to allow non logging configs * update contributors * Auto Format * update test files * Auto Format * update test files incluede region * Auto Format * pr comments - formatting and var name change Co-authored-by: cloudpossebot <11232728+cloudpossebot@users.noreply.github.com>
* remove outputs * Auto Format Co-authored-by: cloudpossebot <11232728+cloudpossebot@users.noreply.github.com>
@Makeshift @dylanbannon we did a rebased to fix the conflicts due to your latest changes and hot-fixes, but still having issue with you CI/CD validation. We checked form side but we are not clear about what permission is needed by cloudpossebot in our repo. In fact the forked repo is public https://github.com/binbashar/terraform-aws-firewall-manager Can you help us with this in order to contribute to your module? Thanks in advance! |
This pull request is now in conflict. Could you fix it @lgallard? 🙏 |
@lgallard you'll have to run |
@lgallard wrote
See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork for details about allowing us to modify your PR. |
@Nuru @nitrocode conflicts were fixed. On the other hand I cound't find the option you pointed it out in here https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork Please let us know if we need to do anything else to close the PR 🙏🏻 |
@lgallard according to github, there are still conflicts. Could you look it over again ? |
@lgallard Sorry about the difficulty getting this PR formatted and merged. Because we cannot push to your branch, we and our automated tools are not able to fix these issues for you. You need to resolve the conflicts as explained by GitHub, and again run
and then commit and push the result. Note: any conflicts in
before running |
@Nuru thank you! That works for us. I hope next PRs we can find the permission issue on our end. |
what
include_map
andexclude_map
attributesshiled
typowhy
references