Skip to content
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

Vnext release #14

Merged
merged 6 commits into from
Dec 6, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions .github/workflows/check-links.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
name: Check Markdown links

#on:
# push:
# branches:
# - master
# pull_request:
# branches: [master]
on: push
jobs:
markdown-link-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: technote-space/get-diff-action@v6
with:
PATTERNS: |
**/**.md

- uses: gaurav-nelson/github-action-markdown-link-check@v1
with:
use-quiet-mode: 'yes'
use-verbose-mode: 'yes'
config-file: '.md_check_config.json'

14 changes: 14 additions & 0 deletions .md_check_config.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
{
"ignorePatterns": [
{
"pattern": "^http://localhost"
}
],
"replacementPatterns": [
{
"pattern": "^/LICENSE",
"replacement": "{{BASEURL}}/LICENSE"
}
],
"timeout": "20s"
}
21 changes: 21 additions & 0 deletions .pre-commit-config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# This is an example configuration to enable detect-secrets in the pre-commit hook.
# Add this file to the root folder of your repository.
#
# Read pre-commit hook framework https://pre-commit.com/ for more details about the structure of config yaml file and how git pre-commit would invoke each hook.
#
# This line indicates we will use the hook from ibm/detect-secrets to run scan during committing phase.
repos:
- repo: https://github.com/ibm/detect-secrets
# If you desire to use a specific version of detect-secrets, you can replace `master` with other git revisions such as branch, tag or commit sha.
# You are encouraged to use static refs such as tags, instead of branch name
#
# Running "pre-commit autoupdate" automatically updates rev to latest tag
rev: 0.13.1+ibm.62.dss
hooks:
- id: detect-secrets # pragma: whitelist secret
# Add options for detect-secrets-hook binary. You can run `detect-secrets-hook --help` to list out all possible options.
# You may also run `pre-commit run detect-secrets` to preview the scan result.
# when "--baseline" without "--use-all-plugins", pre-commit scan with just plugins in baseline file
# when "--baseline" with "--use-all-plugins", pre-commit scan with all available plugins
# add "--fail-on-unaudited" to fail pre-commit for unaudited potential secrets
args: [--baseline, .secrets.baseline, --use-all-plugins]
96 changes: 96 additions & 0 deletions .secrets.baseline
Original file line number Diff line number Diff line change
@@ -0,0 +1,96 @@
{
"exclude": {
"files": "^.secrets.baseline$",
"lines": null
},
"generated_at": "2024-08-09T13:05:01Z",
"plugins_used": [
{
"name": "AWSKeyDetector"
},
{
"name": "ArtifactoryDetector"
},
{
"name": "AzureStorageKeyDetector"
},
{
"base64_limit": 4.5,
"name": "Base64HighEntropyString"
},
{
"name": "BasicAuthDetector"
},
{
"name": "BoxDetector"
},
{
"name": "CloudantDetector"
},
{
"ghe_instance": "github.ibm.com",
"name": "GheDetector"
},
{
"name": "GitHubTokenDetector"
},
{
"hex_limit": 3,
"name": "HexHighEntropyString"
},
{
"name": "IbmCloudIamDetector"
},
{
"name": "IbmCosHmacDetector"
},
{
"name": "JwtTokenDetector"
},
{
"keyword_exclude": null,
"name": "KeywordDetector"
},
{
"name": "MailchimpDetector"
},
{
"name": "NpmDetector"
},
{
"name": "PrivateKeyDetector"
},
{
"name": "SlackDetector"
},
{
"name": "SoftlayerDetector"
},
{
"name": "SquareOAuthDetector"
},
{
"name": "StripeDetector"
},
{
"name": "TwilioKeyDetector"
}
],
"results": {
"doc/topics/tut_icp_gs_odm_cp4ba_prereqs.md": [
{
"hashed_secret": "f44217a81173869e08671753c52553646ff5d95b",
"is_secret": false,
"is_verified": false,
"line_number": 66,
"type": "Secret Keyword",
"verified_result": null
}
]
},
"version": "0.13.1+ibm.62.dss",
"word_list": {
"file": null,
"hash": null
}
}
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@

This tutorial is for technical and business users who want an introduction to business rules authoring and management with IBM Operational Decision Manager (ODM) running in a container environment. Here are the different offerings where you can use this Getting Started tutorial:
* [IBM Operational Decision Manager for Developers](https://hub.docker.com/r/ibmcom/odm/) - To deploy ODM in Docker environments, for evaluation and development purposes.
* [IBM Operational Decision Manager for Developers on Certified Kubernetes](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/24.0.0) - To deploy ODM on Certified Kubernetes environments, for evaluation and development purposes.
* [IBM Operational Decision Manager for Developers on Certified Kubernetes](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/24.0.1) - To deploy ODM on Certified Kubernetes environments, for evaluation and development purposes.
* [IBM Operational Decision Manager for production on Certified Kubernetes](https://www.ibm.com/docs/en/odm/9.0.0?topic=kubernetes-installing-odm-production) - To deploy ODM on Certified Kubernetes environments, for production use.
* [IBM Operational Decision Manager in IBM Cloud Pak for Business Automation in starter mode](https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.0?topic=deployments-installing-cp4ba-multi-pattern-starter-deployment) - To deploy ODM on RedHat OpenShift in the context of IBM Cloud Pak for Business Automation in starter mode.
* [IBM Operational Decision Manager in IBM Cloud Pak for Business Automation in starter mode](https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=deployments-installing-cp4ba-multi-pattern-starter-deployment) - To deploy ODM on RedHat OpenShift in the context of IBM Cloud Pak for Business Automation in starter mode.


## Time required
Expand Down Expand Up @@ -39,7 +39,7 @@ This tutorial uses the Miniloan Service decision service. To further explore the

## Issues and contributions

For issues specifically related to this tutorial, please use the [GitHub issue tracker](https://github.com/DecisionsDev/odm-for-container-getting-started/issues). For more general issues related to IBM Operational Decision Manager, you can [get help]([https://developer.ibm.com/odm/home/connect/](https://community.ibm.com/community/user/automation/communities/community-home?CommunityKey=c0005a22-520b-4181-bfad-feffd8bdc022)) from the ODM community or, if you own production licenses for Operational Decision Manager, through the usual support channels.
For issues specifically related to this tutorial, please use the [GitHub issue tracker](https://github.com/DecisionsDev/odm-for-container-getting-started/issues). For more general issues related to IBM Operational Decision Manager, you can [get help](https://community.ibm.com/community/user/automation/communities/community-home?communitykey=c0005a22-520b-4181-bfad-feffd8bdc022) from the ODM community or, if you own production licenses for Operational Decision Manager, through the usual support channels.

## Licensing information

Expand Down
Loading