-
Notifications
You must be signed in to change notification settings - Fork 2
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
Automatically deploy contents to the development stage when changes are merged #4
Comments
AWS CodePipeline comes in. |
Pipeline steps,
|
I am going to initialize a separate CDK stack in a new |
How can I avoid duplicating |
How about to use |
We have to be careful about the version of node modules installed in a linked package. If the host package and linked package share dependencies, their version must agree. |
I think I have hit this issue related to |
I do not have to stick to |
I am still getting the following error,
No dependencies of the linked package are installed whether I use |
I think I have hit another serious bug. |
I managed to circumvent the problem with |
I wanted to loosely link the |
I am going to connect the pipeline to this GitHub repository via CodeStartSourceConnection. And I have to learn about AWS CodeStar. |
Hmm.. I have to create an Amazon developer account to create a project with AWS CodeStar. Can I use only a GitHub connection that I have created during project creation without finishing the creation? Give it a shot anyway. |
I have to figure out how to run Zola with AWS CodeBuild. |
Zola provides a Docker image. |
At least, I can list my GitHub connection with |
I do not think I can rely on that image because |
How about to use Alpine Linux that is available at Amazon ECR Public Gallery. I have confirmed that Zola can be easily installed on that image through the |
The operation CDK stack needs to know the following information,
The above information can be obtained from the main CDK stacks because they output the above information. |
We may tighten the link between the main CDK stacks and the operation CDK stack by exporting that information from the former to the latter. However, I had a bitter experience with exports in the past. It prohibited replacing the exported resources until the reference from the other stack was removed. So I am discouraged from exporting resources from a CloudFormation stack. |
- A new local package `cdk-common` that collects types and functions shared among CDK stacks in this repository is introduced. It provides the type `DeploymentStage` so far. - A new CDK stack for continuous delivery is going to be introduced, and it will share some stuff like `DeploymentStage` with the CDK stack in the `cdk` folder. - `cdk-common` is supposed to be locally linked from other projects with `npm link --save ../cdk-common`. There was an issue with the `prepare` life cycle script that no dependencies of `cdk-common` were installed before running the `prepare` script and the `prepare` script ended up with a build error. The `scripts/prepare.js` script circumvents this situation by invoking `npm install` if there is no `node_modules` folder in this project. See comments in `script/prepare.js` for more details. issue codemonger-io#4
- The `cdk-common` package is locally linked with `npm link --save ../cdk-common`. issue codemonger-io#4
- `DeploymentStage` and related functions are replaced with the ones defined in `cdk-common`. issue codemonger-io#4
- `README.md` briefly explains this library. issue codemonger-io#4
- `cdk-common` is linked. - `aws-cdk` and `aws-cdk-lib` are bumped to 2.28.1. - `constructs` is bumped to 10.1.42. issue codemonger-io#4
- The CDK stack is renamed to `codemonger-operation`. issue codemonger-io#4
- `@aws-sdk/client-cloudformation` is installed so that the CDK script can obtain outputs from the main stacks. issue codemonger-io#4
- A new CDK construct `ContentsPipeline` that provisions a CodePipeline pipeline that automates the workflow to update the contents of the codemonger website is introduced. - A new CDK construct `CodemongerResources` that resolves resources in the main codemonger stacks is defined in a new file `lib/codemonger-resources.ts`. The file `lib/codemonger-resources.ts` also provides a function `resolveCodemongerResourceNames` that resolves the resource names in the main codemonger stacks by obtaining outputs from the stacks. `bin/cdk-ops.ts` invokes `resolveCodemongerResourceNames` and passes results to the constructor of `CdkOpsStack`. - You have to prepare an untracked file (in `.gitignore`) `lib/github-connection-config.ts` that provides information to connect the pipeline and this GitHub repository. issue codemonger-io#4
- `README.md` and `README.ja.md` explain how to deploy this CDK stack. They also provide the following information, - About the workflow to be automated - Why exports of CloudFormation are not used issue codemonger-io#4
- `README.md` and `README.ja.md` explain what we have to do when we update the library. issue codemonger-io#4
- `README.md` and `README.ja.md` add a link to the subfolder `cdk-ops`. issue codemonger-io#4
It would be nice if
The text was updated successfully, but these errors were encountered: