@rio-cloud/cdk-v2-constructs 1.0.1-alpha.0 → 1.0.1

package/.jsii

@@ -2977,7 +2977,7 @@
   },
   "name": "@rio-cloud/cdk-v2-constructs",
   "readme": {
-    "markdown": "# RIO CDK Constructs\n\nThis package contains CDK constructs RIO teams.\n\n> NPM: `@rio-cloud/cdk-v2-constructs`\n\n## CDK Bootstrapping\n\n```\n$ cdk init --language typescript\n```\n\n## Installing\n\n```\n$ npm install --save @rio-cloud/cdk-v2-constructs\n```\n\n## Constructs\n\nSee [./API.md](API.md) for a list of constructs\n\n## Open issues\n\n- DataDog: Use DataDog.jar inside Docker image for profiling (using AWS Artifacts?)\n- Add vulnerability and license-check actions\n- Get self-signed certificate for LB<->Service communication\n\n- DataDog: Provide aspect to use lambda extensions to send logs to DataDog\n- Introduce immutable tags to RioEcrRepo (waits for https://github.com/aws/aws-cdk/pull/10557))\n- Replace custom synth action with standard one, once [CDK #12061](https://github.com/aws/aws-cdk/issues/12061) is fixed\n\n- Have custom resource to create BitBucket repo and webhook automatically\n- Send container image scan results to OpsGenie\n- Check for security requirements (s3 buckets, ...) - maybe automated as aspect?\n- RDS: Provide RIO-style Aurora\n- Backup: Provide aspect to add automatically backup tags\n- Send build status back to BitBucket (see cdk-codepipeline-bitbucket-build-result-reporter)\n- Support PR builds (using StepFunctions?)\n- Move this library to AWS CodeArtifact\n\n## Developing CDK libraries\n\nProvide commit messages according to [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). This library uses [standard-version](https://github.com/conventional-changelog/standard-version) to generate the changelog and publish a new version.\nExample commit message:\n```shell\nfix(watchful): :bug: removing toggle rioclaid-1857-datadog-threshold; removed threshold\nrioclaid-1857\n```\n\n## Releasing a new version\n\nMake sure that the parameter store `/config/npm/token` having the npm token to publish is added before releasing.\n\n1. Create locally a new release by running `npm run release`. (e.g. `npm run release -- --release-as minor`)\n2. Check the generated `CHANGELOG.md` file and adjust thing when necessary\n"
+    "markdown": "# RIO CDK Constructs\n\nThis package contains CDK2 constructs for RIO teams.\n\n> NPM: `@rio-cloud/cdk-v2-constructs`\n\n## Bootstrapping of CDK project\n\n```\n$ npx cdk init --language typescript\n```\n\n## Installation\n\n```\n$ npm install --save @rio-cloud/cdk-v2-constructs\n```\n\n## See also\n\n * [How to contribut](./CONTRIBUTION.md)\n * [Changelog](./CHANGELOG.md)\n * [brief API desciption](./API.md)\n"
   },
   "repository": {
     "type": "git",
@@ -7828,5 +7828,5 @@
     }
   },
   "version": "0.0.0",
-  "fingerprint": "LZjWae6g6gHUDCt8T/XXOzgUXkQKKVbnNSt11J0P2YY="
+  "fingerprint": "zyDodGYSizYcqBXwixejIlGksAP/sgYU/oJjXveAZTI="
 }

package/CHANGELOG.md

@@ -2,4 +2,6 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+### [1.0.1](https://collaboration.msi.audi.com/stash/projects/RIODEV/repos/cdk-v2-constructs/compare/commits?targetBranch=refs%2Ftags%2Fv1.0.1-alpha.0&sourceBranch=refs%2Ftags%2Fv1.0.1) (2022-04-07)
+
 ### [1.0.1-alpha.0](https://collaboration.msi.audi.com/stash/projects/RIODEV/repos/cdk-v2-constructs/compare/commits?targetBranch=refs%2Ftags%2Fv0.10.63&sourceBranch=refs%2Ftags%2Fv1.0.1-alpha.0) (2022-04-06)

package/CONTRIBUTION.md

@@ -0,0 +1,15 @@
+## Developing CDK libraries
+
+Provide commit messages according to [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). This library uses [standard-version](https://github.com/conventional-changelog/standard-version) to generate the changelog and publish a new version.
+Example commit message: 
+```shell
+fix(watchful): :bug: removing toggle rioclaid-1857-datadog-threshold; removed threshold
+rioclaid-1857
+```
+
+## Releasing a new version
+
+Make sure that the parameter store `/config/npm/token` having the npm token to publish is added before releasing.
+
+1. Create locally a new release by running `npm run release`. (e.g. `npm run release -- --release-as minor`)
+2. Check the generated `CHANGELOG.md` file and adjust thing when necessary

package/README.md

@@ -1,56 +1,23 @@
 # RIO CDK Constructs
 
-This package contains CDK constructs RIO teams.
+This package contains CDK2 constructs for RIO teams.
 
 > NPM: `@rio-cloud/cdk-v2-constructs`
 
-## CDK Bootstrapping
+## Bootstrapping of CDK project
 
 ```
-$ cdk init --language typescript
+$ npx cdk init --language typescript
 ```
 
-## Installing
+## Installation
 
 ```
 $ npm install --save @rio-cloud/cdk-v2-constructs
 ```
 
-## Constructs
+## See also
 
-See [./API.md](API.md) for a list of constructs
-
-## Open issues
-
-- DataDog: Use DataDog.jar inside Docker image for profiling (using AWS Artifacts?)
-- Add vulnerability and license-check actions
-- Get self-signed certificate for LB<->Service communication
-
-- DataDog: Provide aspect to use lambda extensions to send logs to DataDog
-- Introduce immutable tags to RioEcrRepo (waits for https://github.com/aws/aws-cdk/pull/10557))
-- Replace custom synth action with standard one, once [CDK #12061](https://github.com/aws/aws-cdk/issues/12061) is fixed
-
-- Have custom resource to create BitBucket repo and webhook automatically
-- Send container image scan results to OpsGenie
-- Check for security requirements (s3 buckets, ...) - maybe automated as aspect?
-- RDS: Provide RIO-style Aurora
-- Backup: Provide aspect to add automatically backup tags
-- Send build status back to BitBucket (see cdk-codepipeline-bitbucket-build-result-reporter)
-- Support PR builds (using StepFunctions?)
-- Move this library to AWS CodeArtifact
-
-## Developing CDK libraries
-
-Provide commit messages according to [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). This library uses [standard-version](https://github.com/conventional-changelog/standard-version) to generate the changelog and publish a new version.
-Example commit message: 
-```shell
-fix(watchful): :bug: removing toggle rioclaid-1857-datadog-threshold; removed threshold
-rioclaid-1857
-```
-
-## Releasing a new version
-
-Make sure that the parameter store `/config/npm/token` having the npm token to publish is added before releasing.
-
-1. Create locally a new release by running `npm run release`. (e.g. `npm run release -- --release-as minor`)
-2. Check the generated `CHANGELOG.md` file and adjust thing when necessary
+ * [How to contribut](./CONTRIBUTION.md)
+ * [Changelog](./CHANGELOG.md)
+ * [brief API desciption](./API.md)

package/package.json

@@ -15,7 +15,7 @@
   ],
   "main": "lib/index.js",
   "license": "Apache-2.0",
-  "version": "1.0.1-alpha.0",
+  "version": "1.0.1",
   "types": "lib/index.d.ts",
   "stability": "stable",
   "jsii": {

package/version.json

@@ -1,3 +1,3 @@
 {
-  "version": "1.0.1-alpha.0"
+  "version": "1.0.1"
 }