aws-cdk-constructs 2.30.1__tar.gz → 2.30.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (56) hide show
  1. aws_cdk_constructs-2.30.2/PKG-INFO +122 -0
  2. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/__init__.py +1 -1
  3. aws_cdk_constructs-2.30.2/aws_cdk_constructs.egg-info/PKG-INFO +122 -0
  4. aws_cdk_constructs-2.30.1/PKG-INFO +0 -119
  5. aws_cdk_constructs-2.30.1/aws_cdk_constructs.egg-info/PKG-INFO +0 -119
  6. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/LICENSE.txt +0 -0
  7. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/MANIFEST.in +0 -0
  8. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/README.md +0 -0
  9. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/api/__init__.py +0 -0
  10. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/api/api.py +0 -0
  11. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/__init__.py +0 -0
  12. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/auth_flow.py +0 -0
  13. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/base_edge_constructs.py +0 -0
  14. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/bucket.py +0 -0
  15. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/configuration.py +0 -0
  16. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/edge_function.py +0 -0
  17. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/edge_role.py +0 -0
  18. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/log_level.py +0 -0
  19. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/secret_generator.py +0 -0
  20. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/bucket/with_configuration.py +0 -0
  21. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/__init__.py +0 -0
  22. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/_types/__init__.py +0 -0
  23. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/_types/document.py +0 -0
  24. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/_types/graph.py +0 -0
  25. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/_types/relational.py +0 -0
  26. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/database.py +0 -0
  27. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/database/types.py +0 -0
  28. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/ecs/__init__.py +0 -0
  29. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/ecs/cluster.py +0 -0
  30. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/ecs/fargate_validator.py +0 -0
  31. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/ecs/microservice.py +0 -0
  32. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/efs/__init__.py +0 -0
  33. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/efs/volume.py +0 -0
  34. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/load_balancer/__init__.py +0 -0
  35. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/load_balancer/alb.py +0 -0
  36. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/load_balancer/nlb.py +0 -0
  37. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/microservice/__init__.py +0 -0
  38. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/microservice/base_user_data.sh +0 -0
  39. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/microservice/manage_connection_to_nlb_instance_security_group_ingress/lambda_function.js +0 -0
  40. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/microservice/microservice.py +0 -0
  41. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/security_group/__init__.py +0 -0
  42. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/security_group/security_group.py +0 -0
  43. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/service_user_for_iac/__init__.py +0 -0
  44. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/service_user_for_iac/service_user_for_iac.py +0 -0
  45. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/service_user_for_static_assets/__init__.py +0 -0
  46. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/service_user_for_static_assets/service_user_for_static_assets.py +0 -0
  47. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/utils.py +0 -0
  48. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/windows_server/__init__.py +0 -0
  49. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/windows_server/user_data.ps1 +0 -0
  50. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs/windows_server/windows_server.py +0 -0
  51. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs.egg-info/SOURCES.txt +0 -0
  52. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs.egg-info/dependency_links.txt +0 -0
  53. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs.egg-info/requires.txt +0 -0
  54. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/aws_cdk_constructs.egg-info/top_level.txt +0 -0
  55. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/setup.cfg +0 -0
  56. {aws_cdk_constructs-2.30.1 → aws_cdk_constructs-2.30.2}/setup.py +0 -0
@@ -0,0 +1,122 @@
1
+ Metadata-Version: 2.1
2
+ Name: aws_cdk_constructs
3
+ Version: 2.30.2
4
+ Summary: AWS CDK constructs
5
+ Home-page: https://bitbucket.org/cioapps/aws-cdk-constructs
6
+ Author: author
7
+ Author-email: author@foa.org
8
+ License: UNKNOWN
9
+ Platform: UNKNOWN
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: License :: OSI Approved :: Apache Software License
13
+ Classifier: Programming Language :: JavaScript
14
+ Classifier: Programming Language :: Python :: 3 :: Only
15
+ Classifier: Programming Language :: Python :: 3.6
16
+ Classifier: Programming Language :: Python :: 3.7
17
+ Classifier: Programming Language :: Python :: 3.8
18
+ Classifier: Topic :: Software Development :: Code Generators
19
+ Classifier: Topic :: Utilities
20
+ Classifier: Typing :: Typed
21
+ Requires-Python: >=3.6
22
+ Description-Content-Type: text/markdown
23
+ License-File: LICENSE.txt
24
+
25
+
26
+
27
+ # Start here
28
+ FAO AWS CDK is library to build FAO-compliant AWS infrastructure in near-zero time-to-market.
29
+
30
+ CSI Cloud Team developed a set of highly reusable AWS infrastructural building-blocks in collaboration with the Unix Admin Team and Statistical Working System (SWS) development team.
31
+
32
+ To adopt FAO AWS CDK enhances the projects' robustness over the time as they will inherit the benefits of a centralized infrastructural development, they can keep the focus on application features development.
33
+
34
+ These shared infrastructural building-blocks natively implement FAO AWS best practices and abstract low-level technical details, while enabling AWS developers to focus on code production.
35
+
36
+ As a major positive side effect, the overal sustainability of the FAO AWS cloud environment reaches the stars 🚀.
37
+
38
+ - [Python package index of FAO AWS CDK](https://pypi.org/project/aws-cdk-constructs/)
39
+ - [Source on Bitbucket of FAO AWS CDK](https://bitbucket.org/cioapps/aws-cdk-constructs)
40
+
41
+ ## Prerequisites
42
+ Make sure your local machine is configured to meet the [FAO AWS prerequisites](https://aws.fao.org/docs/cdk/introduction/#prerequisites)
43
+ and you have a general undestanding of what AWS CDK is and how to use it.
44
+
45
+ - [AWS CDK introuction](https://aws.amazon.com/cdk/)
46
+ - [AWS CDK - YouTube video](https://www.youtube.com/watch?time_continue=1&v=bz4jTx4v-l8)
47
+ - [AWS CDK Workshop - Python](https://cdkworkshop.com/30-python.html)
48
+
49
+ ## Documentation, reference architectures, tutorials, and more
50
+
51
+ CSI Cloud Team produced extensive documentation about FAO AWS CDK (and FAO AWS in general).
52
+ - [FAO CDK intro](https://aws.fao.org/docs/cdk/introduction/).
53
+ - [FAO CDK project structure](https://aws.fao.org/docs/cdk/project_structure/).
54
+ - [FAO CDK reference architectures, ready to be copied](https://aws.fao.org/docs/cdk/reference_architectures/).
55
+ - [Common issues and troubleshooting with FAO CDK](https://aws.fao.org/docs/cdk/troubleshooting/).
56
+ - [Video tutorials](https://aws.fao.org/docs/tutorials/video_tutorials/).
57
+
58
+ ## Getting started
59
+
60
+ ### Local project initialization
61
+
62
+ - If you project is officially started, you can request a new Bitbucket.org repo for you cloud infrastructure
63
+ - CSI Cloud Team created a [skeleon project](https://bitbucket.org/cioapps/aws-cdk-template-iac) to simplify the onboarding to FAO CDK and what the repository will contains will be identical to [this](https://bitbucket.org/cioapps/aws-cdk-template-iac). The repository will be already configured to implement CD/CI;
64
+ - Browser the `app.py` file to examples of how to intantiate FAO CDK resources with relative explainations
65
+ - Follow the [FAO Development lifecycle](https://aws.fao.org/docs/csi_managed/development_lifecycle/) to release your cloud solution in the development environment;
66
+ - [Your path towards production](https://aws.fao.org/docs/csi_managed/your_path_towards_production/) describes how to release your solution in the production environment;
67
+ - [The FAO AWS automation](https://aws.fao.org/docs/csi_managed/automation/) website describes in depth how the automation is implemented in the FAO AWS environment.
68
+
69
+ ### Useful commands
70
+
71
+ `<ENV>` possible values: `development`, `qa`, `production`.
72
+
73
+ Kindly note, that the correspondent `.env.<ENV>-iac` file must exist to run a given command. For more information please refer to [How to configure your FAO CDK stack](https://aws.fao.org/docs/cdk/cd_ci/#how-to-configure-your-fao-cdk-stack)
74
+
75
+ - `ENVIRONMENT=<ENV> cdk ls` list all stacks in the app
76
+ - `ENVIRONMENT=<ENV> cdk synth` emits the synthesized CloudFormation template
77
+ - `ENVIRONMENT=<ENV> cdk deploy` deploy this stack to your default AWS account/region
78
+ - `ENVIRONMENT=<ENV> cdk diff` compare deployed stack with current state
79
+ - `ENVIRONMENT=<ENV> cdk docs` open CDK documentation
80
+ - `ENVIRONMENT=<ENV> cdk ls`: to list the available stacks in the projects
81
+ - `ENVIRONMENT=<ENV> cdk synth MY_STACK --profile my-dev`: to synthetize (generate) the cloud formation template of MY_STACK stack
82
+ - `ENVIRONMENT=<ENV> cdk deploy MY_STACK --profile my-dev`: to deploy the MY_STACK stack
83
+
84
+
85
+ ### How to generate the AWS CDK constructs documentation
86
+ The documentation follows Google format.
87
+
88
+ * Browse the `./docs` directory
89
+ * Run the `make html` to generate the static HTML documentation in the `/docs/_build/` directory
90
+
91
+ The documentation release is scripted in the pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published.
92
+
93
+ ### How to release a new version of AWS CDK constructs
94
+
95
+ The release of the constructs in `pypi` is automated in the CD/CI pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published and your constructs available on `pypi`.
96
+ Before to move your code in the `master` branch, remember to upgrade the version of the constructs as following:
97
+ - Commit your changes, each commit in the repository should follow the convention: [https://www.conventionalcommits.org/en/v1.0.0/](https://www.conventionalcommits.org/en/v1.0.0/)
98
+ - Run `npm run release` to auto generate the `CHANGELOG.md` file and upgrade the constructs version.
99
+ - Pull request the code to the master branch of the repo
100
+
101
+ If you try to release a version already published (i.e. you forget to upgrade the package version in the mentioned file) the release will fail.
102
+ Check out the CD/CI pipeline for additional information.
103
+
104
+ ### How can I test my new FAO CDK version before to publish it?
105
+
106
+ - Open the `IAC` project you are working on, and create a `git` branch for the feature you are developing
107
+ - Install the project dependencies using `pip install -r requirements.txt`
108
+ - Locally install the `FAO CDK` constructs using `pip install -e ../../cdk/aws-cdk-constructs/` (NB: the path in your file system may vary). This implies that you cloned the `FAO CDK` repository on your local machine, and the repository is configured to use the `develop` branch
109
+ - Modify in the local `FAO CDK` repo the code to implement the desired infrastructural resources
110
+ - You can test the `FAO CDK` deployment from the `IAC` repository, using the `CDK CLI` (e.g. `cdk deploy YOUR_STACK --profile YOUR_PROFILE`). This will read from your local `FAO CDK` repository the new modifications you just developed to include them in the deployement
111
+ - Once the `FAO CDK` development is completed, release the new `FAO CDK` version as described above and update the `requirements.txt` files in the `IAC` repository
112
+ - Once the `IAC` repository is pushed on Bitbucket, it'll download the newly release `FAO CDK` version during the CD/CI pipeline execution.
113
+
114
+ ### How can I automatically lint my code before each commit
115
+
116
+ There is a check on the pipeline to ensure the code and tests pass the blue linting, to ensure the code is properly formatted you can add the (pre-commit)[./.pre-commit-config.yaml] hook to your local repository.
117
+ ```
118
+ pip install -r requirements-dev.txt
119
+ pre-commit install
120
+ ```
121
+ This will run the linter and lint all the files under aws_cdk_constructs and tests before each commit. If you see that some files failed the tests, blue will automatically fix them for you. You will only have to stage those files back and commit again.
122
+
@@ -14,4 +14,4 @@ from .load_balancer import Alb, Nlb
14
14
  from .security_group import SecurityGroup
15
15
  from .windows_server import WindowsServer
16
16
 
17
- __version__ = '2.30.1'
17
+ __version__ = '2.30.2'
@@ -0,0 +1,122 @@
1
+ Metadata-Version: 2.1
2
+ Name: aws-cdk-constructs
3
+ Version: 2.30.2
4
+ Summary: AWS CDK constructs
5
+ Home-page: https://bitbucket.org/cioapps/aws-cdk-constructs
6
+ Author: author
7
+ Author-email: author@foa.org
8
+ License: UNKNOWN
9
+ Platform: UNKNOWN
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: License :: OSI Approved :: Apache Software License
13
+ Classifier: Programming Language :: JavaScript
14
+ Classifier: Programming Language :: Python :: 3 :: Only
15
+ Classifier: Programming Language :: Python :: 3.6
16
+ Classifier: Programming Language :: Python :: 3.7
17
+ Classifier: Programming Language :: Python :: 3.8
18
+ Classifier: Topic :: Software Development :: Code Generators
19
+ Classifier: Topic :: Utilities
20
+ Classifier: Typing :: Typed
21
+ Requires-Python: >=3.6
22
+ Description-Content-Type: text/markdown
23
+ License-File: LICENSE.txt
24
+
25
+
26
+
27
+ # Start here
28
+ FAO AWS CDK is library to build FAO-compliant AWS infrastructure in near-zero time-to-market.
29
+
30
+ CSI Cloud Team developed a set of highly reusable AWS infrastructural building-blocks in collaboration with the Unix Admin Team and Statistical Working System (SWS) development team.
31
+
32
+ To adopt FAO AWS CDK enhances the projects' robustness over the time as they will inherit the benefits of a centralized infrastructural development, they can keep the focus on application features development.
33
+
34
+ These shared infrastructural building-blocks natively implement FAO AWS best practices and abstract low-level technical details, while enabling AWS developers to focus on code production.
35
+
36
+ As a major positive side effect, the overal sustainability of the FAO AWS cloud environment reaches the stars 🚀.
37
+
38
+ - [Python package index of FAO AWS CDK](https://pypi.org/project/aws-cdk-constructs/)
39
+ - [Source on Bitbucket of FAO AWS CDK](https://bitbucket.org/cioapps/aws-cdk-constructs)
40
+
41
+ ## Prerequisites
42
+ Make sure your local machine is configured to meet the [FAO AWS prerequisites](https://aws.fao.org/docs/cdk/introduction/#prerequisites)
43
+ and you have a general undestanding of what AWS CDK is and how to use it.
44
+
45
+ - [AWS CDK introuction](https://aws.amazon.com/cdk/)
46
+ - [AWS CDK - YouTube video](https://www.youtube.com/watch?time_continue=1&v=bz4jTx4v-l8)
47
+ - [AWS CDK Workshop - Python](https://cdkworkshop.com/30-python.html)
48
+
49
+ ## Documentation, reference architectures, tutorials, and more
50
+
51
+ CSI Cloud Team produced extensive documentation about FAO AWS CDK (and FAO AWS in general).
52
+ - [FAO CDK intro](https://aws.fao.org/docs/cdk/introduction/).
53
+ - [FAO CDK project structure](https://aws.fao.org/docs/cdk/project_structure/).
54
+ - [FAO CDK reference architectures, ready to be copied](https://aws.fao.org/docs/cdk/reference_architectures/).
55
+ - [Common issues and troubleshooting with FAO CDK](https://aws.fao.org/docs/cdk/troubleshooting/).
56
+ - [Video tutorials](https://aws.fao.org/docs/tutorials/video_tutorials/).
57
+
58
+ ## Getting started
59
+
60
+ ### Local project initialization
61
+
62
+ - If you project is officially started, you can request a new Bitbucket.org repo for you cloud infrastructure
63
+ - CSI Cloud Team created a [skeleon project](https://bitbucket.org/cioapps/aws-cdk-template-iac) to simplify the onboarding to FAO CDK and what the repository will contains will be identical to [this](https://bitbucket.org/cioapps/aws-cdk-template-iac). The repository will be already configured to implement CD/CI;
64
+ - Browser the `app.py` file to examples of how to intantiate FAO CDK resources with relative explainations
65
+ - Follow the [FAO Development lifecycle](https://aws.fao.org/docs/csi_managed/development_lifecycle/) to release your cloud solution in the development environment;
66
+ - [Your path towards production](https://aws.fao.org/docs/csi_managed/your_path_towards_production/) describes how to release your solution in the production environment;
67
+ - [The FAO AWS automation](https://aws.fao.org/docs/csi_managed/automation/) website describes in depth how the automation is implemented in the FAO AWS environment.
68
+
69
+ ### Useful commands
70
+
71
+ `<ENV>` possible values: `development`, `qa`, `production`.
72
+
73
+ Kindly note, that the correspondent `.env.<ENV>-iac` file must exist to run a given command. For more information please refer to [How to configure your FAO CDK stack](https://aws.fao.org/docs/cdk/cd_ci/#how-to-configure-your-fao-cdk-stack)
74
+
75
+ - `ENVIRONMENT=<ENV> cdk ls` list all stacks in the app
76
+ - `ENVIRONMENT=<ENV> cdk synth` emits the synthesized CloudFormation template
77
+ - `ENVIRONMENT=<ENV> cdk deploy` deploy this stack to your default AWS account/region
78
+ - `ENVIRONMENT=<ENV> cdk diff` compare deployed stack with current state
79
+ - `ENVIRONMENT=<ENV> cdk docs` open CDK documentation
80
+ - `ENVIRONMENT=<ENV> cdk ls`: to list the available stacks in the projects
81
+ - `ENVIRONMENT=<ENV> cdk synth MY_STACK --profile my-dev`: to synthetize (generate) the cloud formation template of MY_STACK stack
82
+ - `ENVIRONMENT=<ENV> cdk deploy MY_STACK --profile my-dev`: to deploy the MY_STACK stack
83
+
84
+
85
+ ### How to generate the AWS CDK constructs documentation
86
+ The documentation follows Google format.
87
+
88
+ * Browse the `./docs` directory
89
+ * Run the `make html` to generate the static HTML documentation in the `/docs/_build/` directory
90
+
91
+ The documentation release is scripted in the pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published.
92
+
93
+ ### How to release a new version of AWS CDK constructs
94
+
95
+ The release of the constructs in `pypi` is automated in the CD/CI pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published and your constructs available on `pypi`.
96
+ Before to move your code in the `master` branch, remember to upgrade the version of the constructs as following:
97
+ - Commit your changes, each commit in the repository should follow the convention: [https://www.conventionalcommits.org/en/v1.0.0/](https://www.conventionalcommits.org/en/v1.0.0/)
98
+ - Run `npm run release` to auto generate the `CHANGELOG.md` file and upgrade the constructs version.
99
+ - Pull request the code to the master branch of the repo
100
+
101
+ If you try to release a version already published (i.e. you forget to upgrade the package version in the mentioned file) the release will fail.
102
+ Check out the CD/CI pipeline for additional information.
103
+
104
+ ### How can I test my new FAO CDK version before to publish it?
105
+
106
+ - Open the `IAC` project you are working on, and create a `git` branch for the feature you are developing
107
+ - Install the project dependencies using `pip install -r requirements.txt`
108
+ - Locally install the `FAO CDK` constructs using `pip install -e ../../cdk/aws-cdk-constructs/` (NB: the path in your file system may vary). This implies that you cloned the `FAO CDK` repository on your local machine, and the repository is configured to use the `develop` branch
109
+ - Modify in the local `FAO CDK` repo the code to implement the desired infrastructural resources
110
+ - You can test the `FAO CDK` deployment from the `IAC` repository, using the `CDK CLI` (e.g. `cdk deploy YOUR_STACK --profile YOUR_PROFILE`). This will read from your local `FAO CDK` repository the new modifications you just developed to include them in the deployement
111
+ - Once the `FAO CDK` development is completed, release the new `FAO CDK` version as described above and update the `requirements.txt` files in the `IAC` repository
112
+ - Once the `IAC` repository is pushed on Bitbucket, it'll download the newly release `FAO CDK` version during the CD/CI pipeline execution.
113
+
114
+ ### How can I automatically lint my code before each commit
115
+
116
+ There is a check on the pipeline to ensure the code and tests pass the blue linting, to ensure the code is properly formatted you can add the (pre-commit)[./.pre-commit-config.yaml] hook to your local repository.
117
+ ```
118
+ pip install -r requirements-dev.txt
119
+ pre-commit install
120
+ ```
121
+ This will run the linter and lint all the files under aws_cdk_constructs and tests before each commit. If you see that some files failed the tests, blue will automatically fix them for you. You will only have to stage those files back and commit again.
122
+
@@ -1,119 +0,0 @@
1
- Metadata-Version: 2.1
2
- Name: aws_cdk_constructs
3
- Version: 2.30.1
4
- Summary: AWS CDK constructs
5
- Home-page: https://bitbucket.org/cioapps/aws-cdk-constructs
6
- Author: author
7
- Author-email: author@foa.org
8
- License: UNKNOWN
9
- Description:
10
-
11
- # Start here
12
- FAO AWS CDK is library to build FAO-compliant AWS infrastructure in near-zero time-to-market.
13
-
14
- CSI Cloud Team developed a set of highly reusable AWS infrastructural building-blocks in collaboration with the Unix Admin Team and Statistical Working System (SWS) development team.
15
-
16
- To adopt FAO AWS CDK enhances the projects' robustness over the time as they will inherit the benefits of a centralized infrastructural development, they can keep the focus on application features development.
17
-
18
- These shared infrastructural building-blocks natively implement FAO AWS best practices and abstract low-level technical details, while enabling AWS developers to focus on code production.
19
-
20
- As a major positive side effect, the overal sustainability of the FAO AWS cloud environment reaches the stars 🚀.
21
-
22
- - [Python package index of FAO AWS CDK](https://pypi.org/project/aws-cdk-constructs/)
23
- - [Source on Bitbucket of FAO AWS CDK](https://bitbucket.org/cioapps/aws-cdk-constructs)
24
-
25
- ## Prerequisites
26
- Make sure your local machine is configured to meet the [FAO AWS prerequisites](https://aws.fao.org/docs/cdk/introduction/#prerequisites)
27
- and you have a general undestanding of what AWS CDK is and how to use it.
28
-
29
- - [AWS CDK introuction](https://aws.amazon.com/cdk/)
30
- - [AWS CDK - YouTube video](https://www.youtube.com/watch?time_continue=1&v=bz4jTx4v-l8)
31
- - [AWS CDK Workshop - Python](https://cdkworkshop.com/30-python.html)
32
-
33
- ## Documentation, reference architectures, tutorials, and more
34
-
35
- CSI Cloud Team produced extensive documentation about FAO AWS CDK (and FAO AWS in general).
36
- - [FAO CDK intro](https://aws.fao.org/docs/cdk/introduction/).
37
- - [FAO CDK project structure](https://aws.fao.org/docs/cdk/project_structure/).
38
- - [FAO CDK reference architectures, ready to be copied](https://aws.fao.org/docs/cdk/reference_architectures/).
39
- - [Common issues and troubleshooting with FAO CDK](https://aws.fao.org/docs/cdk/troubleshooting/).
40
- - [Video tutorials](https://aws.fao.org/docs/tutorials/video_tutorials/).
41
-
42
- ## Getting started
43
-
44
- ### Local project initialization
45
-
46
- - If you project is officially started, you can request a new Bitbucket.org repo for you cloud infrastructure
47
- - CSI Cloud Team created a [skeleon project](https://bitbucket.org/cioapps/aws-cdk-template-iac) to simplify the onboarding to FAO CDK and what the repository will contains will be identical to [this](https://bitbucket.org/cioapps/aws-cdk-template-iac). The repository will be already configured to implement CD/CI;
48
- - Browser the `app.py` file to examples of how to intantiate FAO CDK resources with relative explainations
49
- - Follow the [FAO Development lifecycle](https://aws.fao.org/docs/csi_managed/development_lifecycle/) to release your cloud solution in the development environment;
50
- - [Your path towards production](https://aws.fao.org/docs/csi_managed/your_path_towards_production/) describes how to release your solution in the production environment;
51
- - [The FAO AWS automation](https://aws.fao.org/docs/csi_managed/automation/) website describes in depth how the automation is implemented in the FAO AWS environment.
52
-
53
- ### Useful commands
54
-
55
- `<ENV>` possible values: `development`, `qa`, `production`.
56
-
57
- Kindly note, that the correspondent `.env.<ENV>-iac` file must exist to run a given command. For more information please refer to [How to configure your FAO CDK stack](https://aws.fao.org/docs/cdk/cd_ci/#how-to-configure-your-fao-cdk-stack)
58
-
59
- - `ENVIRONMENT=<ENV> cdk ls` list all stacks in the app
60
- - `ENVIRONMENT=<ENV> cdk synth` emits the synthesized CloudFormation template
61
- - `ENVIRONMENT=<ENV> cdk deploy` deploy this stack to your default AWS account/region
62
- - `ENVIRONMENT=<ENV> cdk diff` compare deployed stack with current state
63
- - `ENVIRONMENT=<ENV> cdk docs` open CDK documentation
64
- - `ENVIRONMENT=<ENV> cdk ls`: to list the available stacks in the projects
65
- - `ENVIRONMENT=<ENV> cdk synth MY_STACK --profile my-dev`: to synthetize (generate) the cloud formation template of MY_STACK stack
66
- - `ENVIRONMENT=<ENV> cdk deploy MY_STACK --profile my-dev`: to deploy the MY_STACK stack
67
-
68
-
69
- ### How to generate the AWS CDK constructs documentation
70
- The documentation follows Google format.
71
-
72
- * Browse the `./docs` directory
73
- * Run the `make html` to generate the static HTML documentation in the `/docs/_build/` directory
74
-
75
- The documentation release is scripted in the pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published.
76
-
77
- ### How to release a new version of AWS CDK constructs
78
-
79
- The release of the constructs in `pypi` is automated in the CD/CI pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published and your constructs available on `pypi`.
80
- Before to move your code in the `master` branch, remember to upgrade the version of the constructs as following:
81
- - Commit your changes, each commit in the repository should follow the convention: [https://www.conventionalcommits.org/en/v1.0.0/](https://www.conventionalcommits.org/en/v1.0.0/)
82
- - Run `npm run release` to auto generate the `CHANGELOG.md` file and upgrade the constructs version.
83
- - Pull request the code to the master branch of the repo
84
-
85
- If you try to release a version already published (i.e. you forget to upgrade the package version in the mentioned file) the release will fail.
86
- Check out the CD/CI pipeline for additional information.
87
-
88
- ### How can I test my new FAO CDK version before to publish it?
89
-
90
- - Open the `IAC` project you are working on, and create a `git` branch for the feature you are developing
91
- - Install the project dependencies using `pip install -r requirements.txt`
92
- - Locally install the `FAO CDK` constructs using `pip install -e ../../cdk/aws-cdk-constructs/` (NB: the path in your file system may vary). This implies that you cloned the `FAO CDK` repository on your local machine, and the repository is configured to use the `develop` branch
93
- - Modify in the local `FAO CDK` repo the code to implement the desired infrastructural resources
94
- - You can test the `FAO CDK` deployment from the `IAC` repository, using the `CDK CLI` (e.g. `cdk deploy YOUR_STACK --profile YOUR_PROFILE`). This will read from your local `FAO CDK` repository the new modifications you just developed to include them in the deployement
95
- - Once the `FAO CDK` development is completed, release the new `FAO CDK` version as described above and update the `requirements.txt` files in the `IAC` repository
96
- - Once the `IAC` repository is pushed on Bitbucket, it'll download the newly release `FAO CDK` version during the CD/CI pipeline execution.
97
-
98
- ### How can I automatically lint my code before each commit
99
-
100
- There is a check on the pipeline to ensure the code and tests pass the blue linting, to ensure the code is properly formatted you can add the (pre-commit)[./.pre-commit-config.yaml] hook to your local repository.
101
- ```
102
- pip install -r requirements-dev.txt
103
- pre-commit install
104
- ```
105
- This will run the linter and lint all the files under aws_cdk_constructs and tests before each commit. If you see that some files failed the tests, blue will automatically fix them for you. You will only have to stage those files back and commit again.
106
- Platform: UNKNOWN
107
- Classifier: Development Status :: 4 - Beta
108
- Classifier: Intended Audience :: Developers
109
- Classifier: License :: OSI Approved :: Apache Software License
110
- Classifier: Programming Language :: JavaScript
111
- Classifier: Programming Language :: Python :: 3 :: Only
112
- Classifier: Programming Language :: Python :: 3.6
113
- Classifier: Programming Language :: Python :: 3.7
114
- Classifier: Programming Language :: Python :: 3.8
115
- Classifier: Topic :: Software Development :: Code Generators
116
- Classifier: Topic :: Utilities
117
- Classifier: Typing :: Typed
118
- Requires-Python: >=3.6
119
- Description-Content-Type: text/markdown
@@ -1,119 +0,0 @@
1
- Metadata-Version: 2.1
2
- Name: aws-cdk-constructs
3
- Version: 2.30.1
4
- Summary: AWS CDK constructs
5
- Home-page: https://bitbucket.org/cioapps/aws-cdk-constructs
6
- Author: author
7
- Author-email: author@foa.org
8
- License: UNKNOWN
9
- Description:
10
-
11
- # Start here
12
- FAO AWS CDK is library to build FAO-compliant AWS infrastructure in near-zero time-to-market.
13
-
14
- CSI Cloud Team developed a set of highly reusable AWS infrastructural building-blocks in collaboration with the Unix Admin Team and Statistical Working System (SWS) development team.
15
-
16
- To adopt FAO AWS CDK enhances the projects' robustness over the time as they will inherit the benefits of a centralized infrastructural development, they can keep the focus on application features development.
17
-
18
- These shared infrastructural building-blocks natively implement FAO AWS best practices and abstract low-level technical details, while enabling AWS developers to focus on code production.
19
-
20
- As a major positive side effect, the overal sustainability of the FAO AWS cloud environment reaches the stars 🚀.
21
-
22
- - [Python package index of FAO AWS CDK](https://pypi.org/project/aws-cdk-constructs/)
23
- - [Source on Bitbucket of FAO AWS CDK](https://bitbucket.org/cioapps/aws-cdk-constructs)
24
-
25
- ## Prerequisites
26
- Make sure your local machine is configured to meet the [FAO AWS prerequisites](https://aws.fao.org/docs/cdk/introduction/#prerequisites)
27
- and you have a general undestanding of what AWS CDK is and how to use it.
28
-
29
- - [AWS CDK introuction](https://aws.amazon.com/cdk/)
30
- - [AWS CDK - YouTube video](https://www.youtube.com/watch?time_continue=1&v=bz4jTx4v-l8)
31
- - [AWS CDK Workshop - Python](https://cdkworkshop.com/30-python.html)
32
-
33
- ## Documentation, reference architectures, tutorials, and more
34
-
35
- CSI Cloud Team produced extensive documentation about FAO AWS CDK (and FAO AWS in general).
36
- - [FAO CDK intro](https://aws.fao.org/docs/cdk/introduction/).
37
- - [FAO CDK project structure](https://aws.fao.org/docs/cdk/project_structure/).
38
- - [FAO CDK reference architectures, ready to be copied](https://aws.fao.org/docs/cdk/reference_architectures/).
39
- - [Common issues and troubleshooting with FAO CDK](https://aws.fao.org/docs/cdk/troubleshooting/).
40
- - [Video tutorials](https://aws.fao.org/docs/tutorials/video_tutorials/).
41
-
42
- ## Getting started
43
-
44
- ### Local project initialization
45
-
46
- - If you project is officially started, you can request a new Bitbucket.org repo for you cloud infrastructure
47
- - CSI Cloud Team created a [skeleon project](https://bitbucket.org/cioapps/aws-cdk-template-iac) to simplify the onboarding to FAO CDK and what the repository will contains will be identical to [this](https://bitbucket.org/cioapps/aws-cdk-template-iac). The repository will be already configured to implement CD/CI;
48
- - Browser the `app.py` file to examples of how to intantiate FAO CDK resources with relative explainations
49
- - Follow the [FAO Development lifecycle](https://aws.fao.org/docs/csi_managed/development_lifecycle/) to release your cloud solution in the development environment;
50
- - [Your path towards production](https://aws.fao.org/docs/csi_managed/your_path_towards_production/) describes how to release your solution in the production environment;
51
- - [The FAO AWS automation](https://aws.fao.org/docs/csi_managed/automation/) website describes in depth how the automation is implemented in the FAO AWS environment.
52
-
53
- ### Useful commands
54
-
55
- `<ENV>` possible values: `development`, `qa`, `production`.
56
-
57
- Kindly note, that the correspondent `.env.<ENV>-iac` file must exist to run a given command. For more information please refer to [How to configure your FAO CDK stack](https://aws.fao.org/docs/cdk/cd_ci/#how-to-configure-your-fao-cdk-stack)
58
-
59
- - `ENVIRONMENT=<ENV> cdk ls` list all stacks in the app
60
- - `ENVIRONMENT=<ENV> cdk synth` emits the synthesized CloudFormation template
61
- - `ENVIRONMENT=<ENV> cdk deploy` deploy this stack to your default AWS account/region
62
- - `ENVIRONMENT=<ENV> cdk diff` compare deployed stack with current state
63
- - `ENVIRONMENT=<ENV> cdk docs` open CDK documentation
64
- - `ENVIRONMENT=<ENV> cdk ls`: to list the available stacks in the projects
65
- - `ENVIRONMENT=<ENV> cdk synth MY_STACK --profile my-dev`: to synthetize (generate) the cloud formation template of MY_STACK stack
66
- - `ENVIRONMENT=<ENV> cdk deploy MY_STACK --profile my-dev`: to deploy the MY_STACK stack
67
-
68
-
69
- ### How to generate the AWS CDK constructs documentation
70
- The documentation follows Google format.
71
-
72
- * Browse the `./docs` directory
73
- * Run the `make html` to generate the static HTML documentation in the `/docs/_build/` directory
74
-
75
- The documentation release is scripted in the pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published.
76
-
77
- ### How to release a new version of AWS CDK constructs
78
-
79
- The release of the constructs in `pypi` is automated in the CD/CI pipeline. So you will simply need to release your code in the `master` branch of the repository to see the FAO CDK documentation published and your constructs available on `pypi`.
80
- Before to move your code in the `master` branch, remember to upgrade the version of the constructs as following:
81
- - Commit your changes, each commit in the repository should follow the convention: [https://www.conventionalcommits.org/en/v1.0.0/](https://www.conventionalcommits.org/en/v1.0.0/)
82
- - Run `npm run release` to auto generate the `CHANGELOG.md` file and upgrade the constructs version.
83
- - Pull request the code to the master branch of the repo
84
-
85
- If you try to release a version already published (i.e. you forget to upgrade the package version in the mentioned file) the release will fail.
86
- Check out the CD/CI pipeline for additional information.
87
-
88
- ### How can I test my new FAO CDK version before to publish it?
89
-
90
- - Open the `IAC` project you are working on, and create a `git` branch for the feature you are developing
91
- - Install the project dependencies using `pip install -r requirements.txt`
92
- - Locally install the `FAO CDK` constructs using `pip install -e ../../cdk/aws-cdk-constructs/` (NB: the path in your file system may vary). This implies that you cloned the `FAO CDK` repository on your local machine, and the repository is configured to use the `develop` branch
93
- - Modify in the local `FAO CDK` repo the code to implement the desired infrastructural resources
94
- - You can test the `FAO CDK` deployment from the `IAC` repository, using the `CDK CLI` (e.g. `cdk deploy YOUR_STACK --profile YOUR_PROFILE`). This will read from your local `FAO CDK` repository the new modifications you just developed to include them in the deployement
95
- - Once the `FAO CDK` development is completed, release the new `FAO CDK` version as described above and update the `requirements.txt` files in the `IAC` repository
96
- - Once the `IAC` repository is pushed on Bitbucket, it'll download the newly release `FAO CDK` version during the CD/CI pipeline execution.
97
-
98
- ### How can I automatically lint my code before each commit
99
-
100
- There is a check on the pipeline to ensure the code and tests pass the blue linting, to ensure the code is properly formatted you can add the (pre-commit)[./.pre-commit-config.yaml] hook to your local repository.
101
- ```
102
- pip install -r requirements-dev.txt
103
- pre-commit install
104
- ```
105
- This will run the linter and lint all the files under aws_cdk_constructs and tests before each commit. If you see that some files failed the tests, blue will automatically fix them for you. You will only have to stage those files back and commit again.
106
- Platform: UNKNOWN
107
- Classifier: Development Status :: 4 - Beta
108
- Classifier: Intended Audience :: Developers
109
- Classifier: License :: OSI Approved :: Apache Software License
110
- Classifier: Programming Language :: JavaScript
111
- Classifier: Programming Language :: Python :: 3 :: Only
112
- Classifier: Programming Language :: Python :: 3.6
113
- Classifier: Programming Language :: Python :: 3.7
114
- Classifier: Programming Language :: Python :: 3.8
115
- Classifier: Topic :: Software Development :: Code Generators
116
- Classifier: Topic :: Utilities
117
- Classifier: Typing :: Typed
118
- Requires-Python: >=3.6
119
- Description-Content-Type: text/markdown