|
| 1 | +# Contributing |
| 2 | + |
| 3 | +We welcome contributions to the project. This document provides information and |
| 4 | +guidelines for contributing. |
| 5 | + |
| 6 | +## Development Environment |
| 7 | + |
| 8 | +This repository includes a configuration for a development container using the |
| 9 | +[VS Code Remote - Containers extension](https://code.visualstudio.com/docs/remote/containers). |
| 10 | +This setup allows you to develop within a Docker container that already has all |
| 11 | +the necessary tools and dependencies installed. |
| 12 | + |
| 13 | +The development container is based on Ubuntu 22.04 (Jammy) and includes the |
| 14 | +following tools: |
| 15 | + |
| 16 | +- AWS CLI |
| 17 | +- Node.js |
| 18 | +- TypeScript |
| 19 | +- Docker CLI |
| 20 | +- Terraform |
| 21 | +- Open Policy Agent |
| 22 | + |
| 23 | +### Prerequisites |
| 24 | + |
| 25 | +- [Docker](https://www.docker.com/products/docker-desktop) installed on your |
| 26 | + local machine. |
| 27 | +- [Visual Studio Code](https://code.visualstudio.com/) installed on your |
| 28 | + local machine. |
| 29 | +- [Remote - Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) |
| 30 | + for Visual Studio Code. |
| 31 | + |
| 32 | +### Usage |
| 33 | + |
| 34 | +1. Clone and open this repository: |
| 35 | + |
| 36 | + ```bash |
| 37 | + git clone https://github.com/sgtoj/terraform-aws-cloudfront-middleware-at-edge.git |
| 38 | + code terraform-aws-cloudfront-middleware-at-edge |
| 39 | + ``` |
| 40 | + |
| 41 | +2. When prompted to "Reopen in Container", click "Reopen in Container". This |
| 42 | + will start building the Docker image for the development container. If you're |
| 43 | + not prompted, you can open the Command Palette (F1 or Ctrl+Shift+P), and run |
| 44 | + the "Remote-Containers: Reopen Folder in Container" command. |
| 45 | +
|
| 46 | +3. After the development container is built and started, you can use the |
| 47 | + Terminal in Visual Studio Code to interact with the container. All commands |
| 48 | + you run in the Terminal will be executed inside the container. |
| 49 | +
|
| 50 | +### Troubleshooting |
| 51 | +
|
| 52 | +If you encounter any issues while using the development container, you can try |
| 53 | +rebuilding the container. To do this, open the Command Palette and run the |
| 54 | +"Remote-Containers: Rebuild Container" command. |
| 55 | +
|
| 56 | +## Contribution Guidelines |
| 57 | +
|
| 58 | +We appreciate your interest in contributing to the project. Here are some |
| 59 | +guidelines to help ensure your contributions are accepted. |
| 60 | +
|
| 61 | +### Issues |
| 62 | +
|
| 63 | +- Use the GitHub issue tracker to report bugs or propose new features. |
| 64 | +- Before submitting a new issue, please search to make sure it has not already |
| 65 | + been reported. If it has, add a comment to the existing issue instead of |
| 66 | + creating a new one. |
| 67 | +- When reporting a bug, include as much detail as you can. Include the version |
| 68 | + of the module you're using, what you expected to happen, what actually |
| 69 | + happened, and steps to reproduce the bug. |
| 70 | + |
| 71 | +### Pull Requests |
| 72 | + |
| 73 | +- Submit your changes as a pull request. |
| 74 | +- All pull requests should be associated with an issue. If your change isn't |
| 75 | + associated with an existing issue, please create one before submitting a pull |
| 76 | + request. |
| 77 | +- In your pull request, include a summary of the changes, the issue number it |
| 78 | + resolves, and any additional information that might be helpful for |
| 79 | + understanding your changes. |
| 80 | +- Make sure your changes do not break any existing functionality. If your |
| 81 | + changes require updates to existing tests or the addition of new ones, include |
| 82 | + those in your pull request. |
| 83 | +- Follow the existing code style. We use a linter to maintain code quality, so |
| 84 | + make sure your changes pass the linter checks. |
| 85 | +
|
| 86 | +Thank you for your contributions! |
0 commit comments