@newskit-render/core 2.45.2 → 2.46.0-alpha.1

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 (3) hide show
  1. package/CHANGELOG.md +8 -0
  2. package/infrastructure/INFRASTRUCTURE.md +31 -30
  3. package/package.json +5 -5
package/CHANGELOG.md CHANGED
@@ -3,6 +3,14 @@
3
3
  All notable changes to this project will be documented in this file.
4
4
  See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
5
5
 
6
+ ## [2.45.2](https://github.com/newscorp-ghfb/ncu-newskit-render/compare/@newskit-render/core@2.45.2-alpha.0...@newskit-render/core@2.45.2) (2023-02-28)
7
+
8
+ **Note:** Version bump only for package @newskit-render/core
9
+
10
+
11
+
12
+
13
+
6
14
  ## [2.45.1](https://github.com/newscorp-ghfb/ncu-newskit-render/compare/@newskit-render/core@2.45.1-alpha.2...@newskit-render/core@2.45.1) (2023-02-24)
7
15
 
8
16
  **Note:** Version bump only for package @newskit-render/core
package/infrastructure/INFRASTRUCTURE.md CHANGED
@@ -17,16 +17,17 @@ terraform-ecr/
17
17
  ### Variables
18
18
 
19
19
  You should already have created an entry in the Service Catalogue for your project. The following info is used to tag the AWS resources:
20
+
20
21
  - `<% SERVICE_CATALOGUE_ID >`
21
22
  - `<% SERVICE_NAME >`
22
23
  - `<% ENVIRONMENT >`
23
24
 
24
-
25
25
  `<% PROJECT_NAME >` is used to name the ECR repo and usually is the same as the git repo name
26
26
 
27
27
  ## Helm
28
28
 
29
29
  ### Description
30
+
30
31
  Defines a helm chart for deploying the kubernetes resources needed for the project
31
32
 
32
33
  ```
@@ -51,7 +52,6 @@ helm
51
52
  `templates` folder includes the generalized templates for kubernetes resources and a helpers file defining common variables used in them
52
53
  Different values files include specific values for those templates for different environments.
53
54
 
54
-
55
55
  ### Variables
56
56
 
57
57
  - `<% PROJECT_NAME >` - is used to name the chart and k8s resources and usually is the same as the git repo name
@@ -68,55 +68,56 @@ Provides a sample CircleCI configuration file.
68
68
  .circleci/
69
69
  └── config.yml
70
70
  ```
71
+
71
72
  The configuration uses an inline orb to define most of the job needed for a proper build and deploy workflow.
72
73
 
73
74
  There are 3 workflows:
75
+
74
76
  - pull_request - should be triggered on on pull requests and create separate environment used by devs for features
75
77
 
76
78
  ![pull_request](pull_request.png)
79
+
77
80
  - remove_pr - remove PR environment after merge
78
81
 
79
82
  ![remove_pr](remove_pr.png)
83
+
80
84
  - build_and_depoy - main workflow after feature branch merge to build test and deploy the product
81
85
 
82
86
  ![build_and_deploy](build_and_deploy.png)
83
87
 
84
-
85
88
  ### Variables
86
89
 
87
90
  This configuration relies on getting values from CircleCI contexts. There should be one context per environment in the format: `<% PROJECT_NAME >-<% ENVIRONMENT >`
91
+
88
92
  - stage
89
- - `AWS_ACCESS_KEY_ID` - AWS credentials for EKS cluster
90
- - `AWS_SECRET_ACCESS_KEY` - AWS credentials for EKS cluster
91
- - `AWS_EKS_CLUSTER`- name of eks cluster - ceng-eng-dev
92
- - `AWS_ASSUME_ROLE_ARN` - user role used in EKS cluster
93
- - `AWS_DEFAULT_REGION` - usually eu-west-1
94
- - `GIT_EMAIL` - Github user configuration
95
- - `GIT_USERNAME` - Github user configuration
96
- - `NEWSKIT_API_ENV_URL` - Newskit API configuration
97
- - `NEWSKIT_API_X_API_KEY` - Newskit API configuration
93
+ - `AWS_ACCESS_KEY_ID` - AWS credentials for EKS cluster
94
+ - `AWS_SECRET_ACCESS_KEY` - AWS credentials for EKS cluster
95
+ - `AWS_EKS_CLUSTER`- name of eks cluster - ceng-eng-dev
96
+ - `AWS_ASSUME_ROLE_ARN` - user role used in EKS cluster
97
+ - `AWS_DEFAULT_REGION` - usually eu-west-1
98
+ - `GIT_EMAIL` - Github user configuration
99
+ - `GIT_USERNAME` - Github user configuration
100
+ - `NEWSKIT_API_ENV_URL` - Newskit API configuration
101
+ - `NEWSKIT_API_X_API_KEY` - Newskit API configuration
98
102
  - dev - same as stage plus the following:
99
- - `AWS_ACCOUNT_ID` - The account id for ECR repo
100
- - `ECR_AWS_ACCESS_KEY_ID` - AWS credentials for ECR
101
- - `ECR_AWS_SECRET_ACCESS_KEY` - AWS credentials for ECR
102
- - `ECR_AWS_ASSUME_ROLE_ARN` - AWS role for ECR
103
- - `PACT_BROKER_TOKEN` - pact broker configuration
104
- - `PACT_BROKER_URL` - pact broker configuration
103
+ - `AWS_ACCOUNT_ID` - The account id for ECR repo
104
+ - `ECR_AWS_ACCESS_KEY_ID` - AWS credentials for ECR
105
+ - `ECR_AWS_SECRET_ACCESS_KEY` - AWS credentials for ECR
106
+ - `ECR_AWS_ASSUME_ROLE_ARN` - AWS role for ECR
107
+ - `PACT_BROKER_TOKEN` - pact broker configuration
108
+ - `PACT_BROKER_URL` - pact broker configuration
105
109
  - prod - same as stage plus the following
106
- - `BOOK_RELEASE_ROLE_ARN` - AWS IAM role giving access to S3 bucket with release sheet credentials
107
- - `GIT_ACCESS_TOKEN` - Github personal access token used to created releases
108
- - `GIT_EMAIL` - Email for user creating releases
109
- - `GIT_USERNAME` - Username for user creating releases
110
- - `PRODUCT_OWNER` - Product owner used for releases - needs to be in Remedy on Demand
111
- - `RELEASE_AWS_ACCESS_KEY_ID` - AWS credentials for release role
112
- - `RELEASE_AWS_SECRET_ACCESS_KEY` - AWS credentials for release role
113
- - `ROD_ENVIRONMENT` - Remedy on Demand configuration
114
- - `ROD_PASSWORD` - Remedy on Demand credentials
115
- - `ROD_USERNAME` - Remedy on Demand credentials
116
- - `ROD_TEMPLATEID`- Remedy on Demand configuration
117
- - `SLACK_RELEASES_WEBHOOK` - Webhook for releases slack channel
110
+ - `BOOK_RELEASE_ROLE_ARN` - AWS IAM role giving access to S3 bucket with release sheet credentials
111
+ - `GIT_ACCESS_TOKEN` - Github personal access token used to created releases
112
+ - `GIT_EMAIL` - Email for user creating releases
113
+ - `GIT_USERNAME` - Username for user creating releases
114
+ - `PRODUCT_OWNER` - Product owner used for releases - needs to be in Remedy on Demand
115
+ - `RELEASE_AWS_ACCESS_KEY_ID` - AWS credentials for release role
116
+ - `RELEASE_AWS_SECRET_ACCESS_KEY` - AWS credentials for release role
117
+ - `SLACK_RELEASES_WEBHOOK` - Webhook for releases slack channel
118
118
 
119
119
  The following placeholders are used in the CircleCI `config.yml` configuration:
120
+
120
121
  - `<% HELM_BUCKET_NAME >` - S3 bucket that is going to host helm charts
121
122
  - `<% HELM_RELEASE_NAME >` - Name of the helm release. Usually alligns with `<% PROJECT_NAME >`
122
123
  - `<% TEAM >`- Used to generate the S3 bucket key i.e. product-platforms
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@newskit-render/core",
3
- "version": "2.45.2",
3
+ "version": "2.46.0-alpha.1",
4
4
  "description": "Newskit Render - Core package",
5
5
  "author": "",
6
6
  "license": "UNLICENSED",
@@ -41,12 +41,12 @@
41
41
  "@emotion/styled": "11.9.3",
42
42
  "@newskit-render/api": "^1.6.6",
43
43
  "@newskit-render/auth": "^1.3.10",
44
- "@newskit-render/checkout": "^2.5.1",
44
+ "@newskit-render/checkout": "^2.5.2-alpha.0",
45
45
  "@newskit-render/feature-flags": "^1.4.11",
46
46
  "@newskit-render/feed": "^1.4.16",
47
- "@newskit-render/my-account": "^4.4.3",
48
- "@newskit-render/shared-components": "^2.5.0",
49
- "@newskit-render/standalone-components": "^2.5.2",
47
+ "@newskit-render/my-account": "^4.4.4-alpha.0",
48
+ "@newskit-render/shared-components": "^2.6.0-alpha.0",
49
+ "@newskit-render/standalone-components": "^2.5.3-alpha.0",
50
50
  "@newskit-render/validation": "^1.5.12",
51
51
  "@next/font": "13.1.6",
52
52
  "cross-fetch": "3.1.5",