yq '.. | ( select (.[] == \"*<target>*\" and keys and parent)) | (path | join(\".\"))' <input file>.yaml \ | sed -E "s@\\.\([0-9]+\)\(\.|$\)@[\\1]\\2@g"
yq '.. | ( select (.[] == "*<target>*" and keys and parent)) | (path | join("."))' <input file>.yaml | sed -E "s@\.([0-9]+)(.|$)@[\1]\2@g"
Output:
objects[0].metadata
https://<keycloak server>/auth/realms/<realm>/protocol/openid-connect/certs.keys[0].x5c[0]curl https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/certs| jq -r ".keys[0].x5c[0]"ServiceMeshControlPlane custom resource, add the CA Certificate as shown below:
apiVersion: maistra.io/v2
kind: ServiceMeshControlPlane
metadata:
| --- | |
| openapi: 3.0.2 | |
| info: | |
| title: Todo | |
| version: 1.0.0 | |
| description: My Todo list API | |
| contact: | |
| url: "http://localhost:8080/api/v1" | |
| email: [email protected] | |
| license: |
| --- | |
| openapi: '3.0.3' | |
| info: | |
| description: Keycloak CRD | |
| title: Keycloak CRD | |
| version: 15.0.1 | |
| paths: | |
| /: | |
| description: test | |
| components: |
Apache Camel is a tool designed to solve implementation of Enterprise Integration Patterns in a simple, consistent, and repeatable manner.
Camel is a framework written for the Java Virtual Machine and it provide many components which can be used to implement your business process. For example, you could translate messages encoded with XML into messages encoded with JSON.
| import groovy.json.JsonSlurper | |
| import groovy.json.JsonOutput | |
| import jenkins.plugins.git.GitSCMSource | |
| import jenkins.plugins.git.traits.BranchDiscoveryTrait | |
| import org.jenkinsci.plugins.workflow.libs.GlobalLibraries | |
| import org.jenkinsci.plugins.workflow.libs.LibraryConfiguration | |
| import org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever | |
| import net.sf.json.JSONObject | |
| /* |
| task runExecutableJar(type: JavaExec) { | |
| // Executable jars can have only _one_ jar on the classpath. | |
| classpath = files(target/cluster-1.0-SNAPSHOT.jar) | |
| // 'main' does not need to be specified | |
| // arguments to pass to the application | |
| args [ | |
| '-cluster', | |
| '-cluster-host', |
Leveraging a multi-container Pod in Jenkins means that we can use external tools like OWASP Zed Attack Proxy. Instead of installing ZAP into each and every potential Jenkins agent container (Maven, Gradle, NPM, etc...), we can use the sidecar pattern to run ZAP alongside whatever build container we would normally used without any changes.
The goal of achieving continuous deployment/delivery is one which many feel uncomfortable with. How can we be assured that the product which is being deployed meets our standards for quality, reliability, and (sometimes most importantly) security? Each stage we add to a CI/CD pipeline is intended to give use further comfort and assurance that our deployed release is up to those standards; but how can we ensure that we are doing all that is needed to analyze for security vulnerabilities? Enter OWASP Zed Attack Proxy, wh
Sometimes it is useful to be able to leverage multiple containers in a Jenkins pipeline instead of modifying a specific container to include additional tools. One example would be using OWASP ZAP to perform penetration testing against web applications and services. Instead of trying to add ZAP into Maven agents and NodeJS agents and whatever other Jenkins agents you might you, you can load a ZAP container as a sidecar.
In OpenShift, Jenkins will automatically detect container images which can be used as agents when it sees ImageStreams which are labeled as shown:
labels:
role: jenkins-slave
| import VueAuthenticate from 'vue-authenticate' | |
| import VueCookies from 'vue-cookies' | |
| export default async ({ Vue }) => { | |
| const authPromise = new Promise(function(resolve, reject) { | |
| Vue.use(VueCookies) | |
| Vue.use(VueAuthenticate, { | |
| baseUrl: 'http://localhost:3000', // Your API domain |