Split (1)

train · 702k rows

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.

Instruction stringlengths 14 778	input_code stringlengths 0 4.24k	output_code stringlengths 1 5.44k
Remove tech preview for odo debugging	[id='debugging-applications-in-odo'] = Debugging applications in `{odo-title}` include::modules/developer-cli-odo-attributes.adoc[] include::modules/common-attributes.adoc[] :context: debugging-applications-in-odo toc::[] :FeatureName: Interactive debugging in {odo-title} include::modules/technology-preview.adoc[leveloffset=+1] With `{odo-title}`, you can attach a debugger to remotely debug your application. This feature is only supported for NodeJS and Java components. Components created with `{odo-title}` run in the debug mode by default. A debugger agent runs on the component, on a specific port. To start debugging your application, you must start port forwarding and attach the local debugger bundled in your Integrated development environment (IDE). include::modules/developer-cli-odo-debugging-an-application.adoc[leveloffset=+1] include::modules/developer-cli-odo-configuring-debugging-parameters.adoc[leveloffset=+1]	[id='debugging-applications-in-odo'] = Debugging applications in `{odo-title}` include::modules/developer-cli-odo-attributes.adoc[] include::modules/common-attributes.adoc[] :context: debugging-applications-in-odo toc::[] With `{odo-title}`, you can attach a debugger to remotely debug your application. This feature is only supported for NodeJS and Java components. Components created with `{odo-title}` run in the debug mode by default. A debugger agent runs on the component, on a specific port. To start debugging your application, you must start port forwarding and attach the local debugger bundled in your Integrated development environment (IDE). include::modules/developer-cli-odo-debugging-an-application.adoc[leveloffset=+1] include::modules/developer-cli-odo-configuring-debugging-parameters.adoc[leveloffset=+1]
Update URL to Groovy Docs	This sample application uses Spring Boot and http://beta.groovy-lang.org/docs/groovy-2.3.1/html/documentation/markup-template-engine.html[Groovy templates] in the View layer. The templates for this app live in `classpath:/templates/`, which is the conventional location for Spring Boot. External configuration is available via ``spring.groovy.template.*''.	This sample application uses Spring Boot and http://docs.groovy-lang.org/latest/html/documentation/#_the_markuptemplateengine[Groovy templates] in the View layer. The templates for this app live in `classpath:/templates/`, which is the conventional location for Spring Boot. External configuration is available via ``spring.groovy.template.*''.
Update to the new {index}/_mapping/{type} format	[[indices-get-mapping]] == Get Mapping The get mapping API allows to retrieve mapping definitions for an index or index/type. [source,js] -------------------------------------------------- curl -XGET 'http://localhost:9200/twitter/_mapping/tweet' -------------------------------------------------- [float] === Multiple Indices and Types The get mapping API can be used to get more than one index or type mapping with a single call. General usage of the API follows the following syntax: `host:port/{index}/{type}/_mapping` where both `{index}` and `{type}` can accept a comma-separated list of names. To get mappings for all indices you can use `_all` for `{index}`. The following are some examples: [source,js] -------------------------------------------------- curl -XGET 'http://localhost:9200/_mapping/twitter,kimchy' curl -XGET 'http://localhost:9200/_all/_mapping/tweet,book' -------------------------------------------------- If you want to get mappings of all indices and types then the following two examples are equivalent: [source,js] -------------------------------------------------- curl -XGET 'http://localhost:9200/_all/_mapping' curl -XGET 'http://localhost:9200/_mapping' --------------------------------------------------	[[indices-get-mapping]] == Get Mapping The get mapping API allows to retrieve mapping definitions for an index or index/type. [source,js] -------------------------------------------------- curl -XGET 'http://localhost:9200/twitter/_mapping/tweet' -------------------------------------------------- [float] === Multiple Indices and Types The get mapping API can be used to get more than one index or type mapping with a single call. General usage of the API follows the following syntax: `host:port/{index}/_mapping/{type}` where both `{index}` and `{type}` can accept a comma-separated list of names. To get mappings for all indices you can use `_all` for `{index}`. The following are some examples: [source,js] -------------------------------------------------- curl -XGET 'http://localhost:9200/_mapping/twitter,kimchy' curl -XGET 'http://localhost:9200/_all/_mapping/tweet,book' -------------------------------------------------- If you want to get mappings of all indices and types then the following two examples are equivalent: [source,js] -------------------------------------------------- curl -XGET 'http://localhost:9200/_all/_mapping' curl -XGET 'http://localhost:9200/_mapping' --------------------------------------------------
Remove link to in-source docs	= Mongo Client image:https://vertx.ci.cloudbees.com/buildStatus/icon?job=vert.x3-mongo-client["Build Status",link="https://vertx.ci.cloudbees.com/view/vert.x-3/job/vert.x3-mongo-client/"] An asynchronous client for interacting with a MongoDB database Please see the in source asciidoc link:vertx-mongo-client/src/main/asciidoc/index.adoc[documentation] or the main documentation on the http://vertx.io/docs/#data_access[web-site] for a full description of Mongo service. The following docker CLI can be used for running mongo tests: ``` docker run --rm --name vertx-mongo -p 27017:27017 mongo ```	= Mongo Client image:https://vertx.ci.cloudbees.com/buildStatus/icon?job=vert.x3-mongo-client["Build Status",link="https://vertx.ci.cloudbees.com/view/vert.x-3/job/vert.x3-mongo-client/"] An asynchronous client for interacting with a MongoDB database Please see the main documentation on the web-site for a full description: * https://vertx.io/docs/vertx-mongo-client/java/[Java documentation] * https://vertx.io/docs/vertx-mongo-client/js/[JavaScript documentation] * https://vertx.io/docs/vertx-mongo-client/kotlin/[Kotlin documentation] * https://vertx.io/docs/vertx-mongo-client/groovy/[Groovy documentation] * https://vertx.io/docs/vertx-mongo-client/ruby/[Ruby documentation] The following docker CLI can be used for running mongo tests: ``` docker run --rm --name vertx-mongo -p 27017:27017 mongo ```
Add link to 2nd part of JAXenter tutorial	# Janitor image:https://travis-ci.org/techdev-solutions/janitor.svg?branch=master["Build Status",link="https://travis-ci.org/techdev-solutions/janitor"] An application to perform cleanup work using the https://getpocket.com[Pocket API]. ## API Documentation The documentation for the Kotlin API bindings can be found https://techdev-solutions.github.io/janitor/pocket-api/[here]. ## Tutorial (German) - https://jaxenter.de/kotlin-tutorial-48156[Kotlin: Ein Tutorial für Einsteiger @ JAXenter]	# Janitor image:https://travis-ci.org/techdev-solutions/janitor.svg?branch=master["Build Status",link="https://travis-ci.org/techdev-solutions/janitor"] An application to perform cleanup work using the https://getpocket.com[Pocket API]. ## API Documentation The documentation for the Kotlin API bindings can be found https://techdev-solutions.github.io/janitor/pocket-api/[here]. ## Tutorial (German) Kotlin: Ein Tutorial für Einsteiger @ JAXenter - https://jaxenter.de/kotlin-tutorial-48156[Part 1] - https://jaxenter.de/kotlin-ein-tutorial-fuer-einsteiger-teil-2-48587[Part 2]
Update userguide: show more levels in the TOC	= Activiti User Guide v 5.17.1-SNAPSHOT :doctype: book :toc: left :icons: font :numbered: :source-highlighter: pygments :pygments-css: class :pygments-linenums-mode: table :compat-mode: include::ch01-Introduction.adoc[] include::ch02-GettingStarted.adoc[] include::ch03-Configuration.adoc[] include::ch04-API.adoc[] include::ch05-Spring.adoc[] include::ch06-Deployment.adoc[] include::ch07a-BPMN-Introduction.adoc[] include::ch07b-BPMN-Constructs.adoc[] include::ch08-Forms.adoc[] include::ch09-JPA.adoc[] include::ch10-History.adoc[] include::ch11-Designer.adoc[] include::ch12-Explorer.adoc[] include::ch13-Modeler.adoc[] include::ch14-REST.adoc[] include::ch15-Cdi.adoc[] include::ch16-Ldap.adoc[] include::ch17-Advanced.adoc[] include::ch18-Simulation.adoc[] include::ch19-operation-control.adoc[]	= Activiti User Guide v 5.17.1-SNAPSHOT :doctype: book :toc: left :toclevels: 5 :icons: font :numbered: :source-highlighter: pygments :pygments-css: class :pygments-linenums-mode: table :compat-mode: include::ch01-Introduction.adoc[] include::ch02-GettingStarted.adoc[] include::ch03-Configuration.adoc[] include::ch04-API.adoc[] include::ch05-Spring.adoc[] include::ch06-Deployment.adoc[] include::ch07a-BPMN-Introduction.adoc[] include::ch07b-BPMN-Constructs.adoc[] include::ch08-Forms.adoc[] include::ch09-JPA.adoc[] include::ch10-History.adoc[] include::ch11-Designer.adoc[] include::ch12-Explorer.adoc[] include::ch13-Modeler.adoc[] include::ch14-REST.adoc[] include::ch15-Cdi.adoc[] include::ch16-Ldap.adoc[] include::ch17-Advanced.adoc[] include::ch18-Simulation.adoc[] include::ch19-operation-control.adoc[]
Fix markup of preformatted text.	= Tiny Git A tiny model of Git, used for learning and demonstrating how Git works. A series of version of Tiny Git is available, in increasing order of complexity. The list of versions and their features is listed below. [options="header"] \|====== \| Version \| Description \| v0 \| Only argument parsing \| v1 \| Implements single file commits without history tracking \| v2 \| Adds support for history tracking and logs \| v3 \| Adds support for checking-out older revisions \| v4 \| Adds support for creating branching \| v5 \| Adds support for merging changes \|====== == Usage The first step is to activate a particular version of Tiny Git. From the top level directory of the project source `activate` and specify the version no. to activate. For example, to activate version `v5`, the following command can be used. ------ $ source activate v5 ------ Type `tig` to get the available list of sub-commands. ------ $ tig Usage: tig init tig commit <msg> tig checkout <start-point> [-b <branch-name>] tig diff tig log tig branch tig merge <branch> ----- == Slides: Building Git From Scratch The link:docs/slides.asciidoc[] provide more information about the various revsions and how to build Git incrementally.	= Tiny Git A tiny model of Git, used for learning and demonstrating how Git works. A series of version of Tiny Git is available, in increasing order of complexity. The list of versions and their features is listed below. [options="header"] \|====== \| Version \| Description \| v0 \| Only argument parsing \| v1 \| Implements single file commits without history tracking \| v2 \| Adds support for history tracking and logs \| v3 \| Adds support for checking-out older revisions \| v4 \| Adds support for creating branching \| v5 \| Adds support for merging changes \|====== == Usage The first step is to activate a particular version of Tiny Git. From the top level directory of the project source `activate` and specify the version no. to activate. For example, to activate version `v5`, the following command can be used. ------ $ source activate v5 ------ Type `tig` to get the available list of sub-commands. ------ $ tig Usage: tig init tig commit <msg> tig checkout <start-point> [-b <branch-name>] tig diff tig log tig branch tig merge <branch> ------ == Slides: Building Git From Scratch The link:docs/slides.asciidoc[] provide more information about the various revsions and how to build Git incrementally.
Update What's New for 5.7	[[new]] = What's New in Spring Security 5.7 Spring Security 5.7 provides a number of new features. Below are the highlights of the release. [[whats-new-servlet]] == Servlet * Web Introduced xref:servlet/authentication/persistence.adoc#requestattributesecuritycontextrepository[`RequestAttributeSecurityContextRepository`] Introduced xref:servlet/authentication/persistence.adoc#securitycontextholderfilter[`SecurityContextHolderFilter`] - Ability to require explicit saving of the `SecurityContext` * OAuth 2.0 Client Allow configuring https://github.com/spring-projects/spring-security/issues/6548[PKCE for confidential clients] Allow configuring a https://github.com/spring-projects/spring-security/issues/9812[JWT assertion resolver] in `JwtBearerOAuth2AuthorizedClientProvider` [[whats-new-webflux]] == WebFlux * OAuth 2.0 Client Allow configuring https://github.com/spring-projects/spring-security/issues/6548[PKCE for confidential clients] Allow configuring a https://github.com/spring-projects/spring-security/issues/9812[JWT assertion resolver] in `JwtBearerReactiveOAuth2AuthorizedClientProvider`	[[new]] = What's New in Spring Security 5.7 Spring Security 5.7 provides a number of new features. Below are the highlights of the release. [[whats-new-servlet]] == Servlet * Web Introduced xref:servlet/authentication/persistence.adoc#requestattributesecuritycontextrepository[`RequestAttributeSecurityContextRepository`] Introduced xref:servlet/authentication/persistence.adoc#securitycontextholderfilter[`SecurityContextHolderFilter`] - Ability to require explicit saving of the `SecurityContext` * OAuth 2.0 Client Allow configuring https://github.com/spring-projects/spring-security/issues/6548[PKCE for confidential clients] Allow configuring a https://github.com/spring-projects/spring-security/issues/9812[JWT assertion resolver] in `JwtBearerOAuth2AuthorizedClientProvider` ** Allow customizing claims on https://github.com/spring-projects/spring-security/issues/9855[JWT client assertions] [[whats-new-webflux]] == WebFlux * OAuth 2.0 Client Allow configuring https://github.com/spring-projects/spring-security/issues/6548[PKCE for confidential clients] Allow configuring a https://github.com/spring-projects/spring-security/issues/9812[JWT assertion resolver] in `JwtBearerReactiveOAuth2AuthorizedClientProvider`
Fix XSD includes: use -1 as end of file indicator	include::common.adoc[] = Ehcache XSDs include::menu.adoc[] == Core [source,xsd,indent=0] ---- include::{sourcedir}/xml/src/main/resources/ehcache-core.xsd[lines=18..260] ---- == JSR-107 extension [source,xsd,indent=0] ---- include::{sourcedir}/107/src/main/resources/ehcache-107ext.xsd[lines=18..44] ----	include::common.adoc[] = Ehcache XSDs include::menu.adoc[] == Core [source,xsd,indent=0] ---- include::{sourcedir}/xml/src/main/resources/ehcache-core.xsd[lines=18..-1] ---- == JSR-107 extension [source,xsd,indent=0] ---- include::{sourcedir}/107/src/main/resources/ehcache-107ext.xsd[lines=18..-1] ----
Remove link to nonexistent ILM API	[[index-lifecycle-management-api]] == Index Lifecycle Management API You can use the following APIs to manage policies on indices. [float] [[ilm-api-policy-endpoint]] === Policy Management APIs * <<ilm-put-lifecycle,Create Lifecycle Policy>> * <<ilm-get-lifecycle,Get Lifecycle Policy>> * <<ilm-delete-lifecycle,Delete Lifecycle Policy>> [float] [[ilm-api-index-endpoint]] === Index Management APIs * <<ilm-move-to-step,Move Index To Step>> * <<ilm-set-policy,Set Policy On Index>> * <<ilm-retry-policy,Retry Policy On Indices>> [float] [[ilm-api-management-endpoint]] === Operation Management APIs * <<ilm-get-status,Get ILM Operation Mode>> * <<ilm-start,Start ILM>> * <<ilm-stop,Stop ILM>> * <<ilm-explain,Explain API>> include::put-lifecycle.asciidoc[] include::get-lifecycle.asciidoc[] include::delete-lifecycle.asciidoc[] include::move-to-step.asciidoc[] include::remove-policy.asciidoc[] include::retry-policy.asciidoc[] include::get-status.asciidoc[] include::explain.asciidoc[] include::start.asciidoc[] include::stop.asciidoc[]	[[index-lifecycle-management-api]] == Index Lifecycle Management API You can use the following APIs to manage policies on indices. [float] [[ilm-api-policy-endpoint]] === Policy Management APIs * <<ilm-put-lifecycle,Create Lifecycle Policy>> * <<ilm-get-lifecycle,Get Lifecycle Policy>> * <<ilm-delete-lifecycle,Delete Lifecycle Policy>> [float] [[ilm-api-index-endpoint]] === Index Management APIs * <<ilm-move-to-step,Move Index To Step>> * <<ilm-retry-policy,Retry Policy On Indices>> [float] [[ilm-api-management-endpoint]] === Operation Management APIs * <<ilm-get-status,Get ILM Operation Mode>> * <<ilm-start,Start ILM>> * <<ilm-stop,Stop ILM>> * <<ilm-explain,Explain API>> include::put-lifecycle.asciidoc[] include::get-lifecycle.asciidoc[] include::delete-lifecycle.asciidoc[] include::move-to-step.asciidoc[] include::remove-policy.asciidoc[] include::retry-policy.asciidoc[] include::get-status.asciidoc[] include::explain.asciidoc[] include::start.asciidoc[] include::stop.asciidoc[]
Update What's New for 6.0	[[new]] = What's New in Spring Security 6.0 Spring Security 6.0 provides a number of new features. Below are the highlights of the release. == Breaking Changes * https://github.com/spring-projects/spring-security/issues/8980[gh-8980] - Remove unsafe/deprecated `Encryptors.querableText(CharSequence,CharSequence)`. Instead use data storage to encrypt values.	[[new]] = What's New in Spring Security 6.0 Spring Security 6.0 provides a number of new features. Below are the highlights of the release. == Breaking Changes * https://github.com/spring-projects/spring-security/issues/8980[gh-8980] - Remove unsafe/deprecated `Encryptors.querableText(CharSequence,CharSequence)`. Instead use data storage to encrypt values. * https://github.com/spring-projects/spring-security/issues/11520[gh-11520] - Remember Me uses SHA256 by default
Update link to puppet module and remove link to other RPM repo as we have our own.	[[misc]] == Misc * https://github.com/electrical/puppet-elasticsearch[Puppet]: Elasticsearch puppet module. * http://github.com/elasticsearch/cookbook-elasticsearch[Chef]: Chef cookbook for Elasticsearch * https://github.com/tavisto/elasticsearch-rpms[elasticsearch-rpms]: RPMs for elasticsearch. * http://www.github.com/neogenix/daikon[daikon]: Daikon Elasticsearch CLI * https://github.com/Aconex/scrutineer[Scrutineer]: A high performance consistency checker to compare what you've indexed with your source of truth content (e.g. DB)	[[misc]] == Misc * https://github.com/elasticsearch/puppet-elasticsearch[Puppet]: Elasticsearch puppet module. * http://github.com/elasticsearch/cookbook-elasticsearch[Chef]: Chef cookbook for Elasticsearch * http://www.github.com/neogenix/daikon[daikon]: Daikon Elasticsearch CLI * https://github.com/Aconex/scrutineer[Scrutineer]: A high performance consistency checker to compare what you've indexed with your source of truth content (e.g. DB)
Add Patreon badge to readme	= griffon-monitor-plugin :linkattrs: :project-name: griffon-monitor-plugin image:http://img.shields.io/travis/griffon-plugins/{project-name}/master.svg["Build Status", link="https://travis-ci.org/griffon-plugins/{project-name}"] image:http://img.shields.io/coveralls/griffon-plugins/{project-name}/master.svg["Coverage Status", link="https://coveralls.io/r/griffon-plugins/{project-name}"] image:http://img.shields.io/badge/license-ASF2-blue.svg["Apache License 2", link="http://www.apache.org/licenses/LICENSE-2.0.txt"] image:https://api.bintray.com/packages/griffon/griffon-plugins/{project-name}/images/download.svg[link="https://bintray.com/griffon/griffon-plugins/{project-name}/_latestVersion"] --- Enables application statistics through JMX. Refer to the link:http://griffon-plugins.github.io/{project-name}/[plugin guide, window="_blank"] for further information on configuration and usage.	= griffon-monitor-plugin :linkattrs: :project-name: griffon-monitor-plugin image:http://img.shields.io/travis/griffon-plugins/{project-name}/master.svg["Build Status", link="https://travis-ci.org/griffon-plugins/{project-name}"] image:http://img.shields.io/coveralls/griffon-plugins/{project-name}/master.svg["Coverage Status", link="https://coveralls.io/r/griffon-plugins/{project-name}"] image:http://img.shields.io/badge/license-ASF2-blue.svg["Apache License 2", link="http://www.apache.org/licenses/LICENSE-2.0.txt"] image:https://api.bintray.com/packages/griffon/griffon-plugins/{project-name}/images/download.svg[link="https://bintray.com/griffon/griffon-plugins/{project-name}/_latestVersion"] --- image:https://img.shields.io/gitter/room/griffon/griffon.js.svg[link="https://gitter.im/griffon/griffon] image:https://img.shields.io/badge/donations-Patreon-orange.svg[https://www.patreon.com/user?u=6609318] --- Enables application statistics through JMX. Refer to the link:http://griffon-plugins.github.io/{project-name}/[plugin guide, window="_blank"] for further information on configuration and usage.
Document ExpectedExceptionSupport bug fix in release notes	[[release-notes-5.1.0-M1]] === 5.1.0-M1 Date of Release: ❓ Scope: ❓ For a complete list of all _closed_ issues and pull requests for this release, consult the link:{junit5-repo}+/milestone/14?closed=1+[5.1 M1] milestone page in the JUnit repository on GitHub. [[release-notes-5.1.0-junit-platform]] ==== JUnit Platform ===== Bug Fixes * ❓ ===== Deprecations and Breaking Changes * ❓ ===== New Features and Improvements * The `junit-platform-surefire-provider` now requires `maven-surefire-plugin` version 2.20.1 or higher. [[release-notes-5.1.0-junit-jupiter]] ==== JUnit Jupiter ===== Bug Fixes * ❓ ===== Deprecations and Breaking Changes * ❓ ===== New Features and Improvements * ❓ [[release-notes-5.1.0-junit-vintage]] ==== JUnit Vintage ===== Bug Fixes * ❓ ===== Deprecations and Breaking Changes * ❓ ===== New Features and Improvements * ❓	[[release-notes-5.1.0-M1]] === 5.1.0-M1 Date of Release: ❓ Scope: ❓ For a complete list of all _closed_ issues and pull requests for this release, consult the link:{junit5-repo}+/milestone/14?closed=1+[5.1 M1] milestone page in the JUnit repository on GitHub. [[release-notes-5.1.0-junit-platform]] ==== JUnit Platform ===== Bug Fixes * ❓ ===== Deprecations and Breaking Changes * ❓ ===== New Features and Improvements * The `junit-platform-surefire-provider` now requires `maven-surefire-plugin` version 2.20.1 or higher. [[release-notes-5.1.0-junit-jupiter]] ==== JUnit Jupiter ===== Bug Fixes * `ExpectedExceptionSupport` from the `junit-jupiter-migrationsupport` module no longer swallows exceptions if the test class does not declare a JUnit 4 `ExpectedException` rule. - Consequently, `@EnableRuleMigrationSupport` and `ExpectedExceptionSupport` may now be used without declaring an `ExpectedException` rule. ===== Deprecations and Breaking Changes * ❓ ===== New Features and Improvements * ❓ [[release-notes-5.1.0-junit-vintage]] ==== JUnit Vintage ===== Bug Fixes * ❓ ===== Deprecations and Breaking Changes * ❓ ===== New Features and Improvements * ❓
Add syskeygen to Elasticsearch Reference	[role="xpack"] [[xpack-commands]] = {xpack} Commands [partintro] -- {xpack} includes commands that help you configure security: * <<certgen>> * <<setup-passwords>> * <<users-command>> -- include::certgen.asciidoc[] include::setup-passwords.asciidoc[] include::users-command.asciidoc[]	[role="xpack"] [[xpack-commands]] = {xpack} Commands [partintro] -- {xpack} includes commands that help you configure security: * <<certgen>> * <<setup-passwords>> * <<syskeygen>> * <<users-command>> -- include::certgen.asciidoc[] include::setup-passwords.asciidoc[] include::syskeygen.asciidoc[] include::users-command.asciidoc[]
Add blog post link to site	spray-kamon-metrics: Better Kamon metrics for your Spray services ================================================================= Daniel Solano_Gómez :description: The spray-kamon-metrics library augments kamon-spray to make it provide more useful metrics, \ particularly by providing Spray can server metrics and better Spray service response metrics. :keywords: kamon, metrics, spray, scala include::../../README.asciidoc[tags=status-badges] include::../../README.asciidoc[tags=preamble] == Documentation * The https://github.com/MonsantoCo/spray-kamon-metrics/blob/master/README.asciidoc[README] on GitHub contains the most comprehensive documentation for using the library. * API documentation link:api/latest[latest] link:api/0.1.2[0.1.2] == Release notes include::../../release-notes.asciidoc[tags=release-notes]	spray-kamon-metrics: Better Kamon metrics for your Spray services ================================================================= Daniel Solano_Gómez :description: The spray-kamon-metrics library augments kamon-spray to make it provide more useful metrics, \ particularly by providing Spray can server metrics and better Spray service response metrics. :keywords: kamon, metrics, spray, scala include::../../README.asciidoc[tags=status-badges] include::../../README.asciidoc[tags=preamble] == Documentation * The https://github.com/MonsantoCo/spray-kamon-metrics/blob/master/README.asciidoc[README] on GitHub contains the most comprehensive documentation for using the library. * API documentation link:api/latest[latest] link:api/0.1.2[0.1.2] * Blog post: http://engineering.monsanto.com/2015/09/24/better-spray-metrics-with-kamon/[Better Spray metrics with Kamon] == Release notes include::../../release-notes.asciidoc[tags=release-notes]
Include M5 document in list of release notes	[[release-notes]] == Release Notes :numbered!: include::release-notes-5.0.0-ALPHA.adoc[] include::release-notes-5.0.0-M1.adoc[] include::release-notes-5.0.0-M2.adoc[] include::release-notes-5.0.0-M3.adoc[] include::release-notes-5.0.0-M4.adoc[] :numbered:	[[release-notes]] == Release Notes :numbered!: include::release-notes-5.0.0-ALPHA.adoc[] include::release-notes-5.0.0-M1.adoc[] include::release-notes-5.0.0-M2.adoc[] include::release-notes-5.0.0-M3.adoc[] include::release-notes-5.0.0-M4.adoc[] include::release-notes-5.0.0-M5.adoc[] :numbered:
Fix Reactive Web link in the ref doc	[[spring-web]] = Web :doc-root: https://docs.spring.io :api-spring-framework: {doc-root}/spring-framework/docs/{spring-version}/javadoc-api/org/springframework :toc: left :toclevels: 2 This part of the documentation covers support for web applications designed to run on a traditional Servlet stack (Servlet API + Servlet container). Chapters cover the Servlet-based <<mvc,Spring MVC>> web framework including <<mvc-view,Views>>, <<mvc-cors,CORS>>, and <<websocket,WebSocket>> support. Note that as of Spring Framework 5.0 web applications can also run on a <<spring-web-reactive, reactive web stack>> (Reactive Streams API + non-blocking runtime). include::web/webmvc.adoc[leveloffset=+1] include::web/webmvc-view.adoc[leveloffset=+1] include::web/webmvc-cors.adoc[leveloffset=+1] include::web/websocket.adoc[leveloffset=+1]	[[spring-web]] = Web :doc-root: https://docs.spring.io :api-spring-framework: {doc-root}/spring-framework/docs/{spring-version}/javadoc-api/org/springframework :toc: left :toclevels: 2 This part of the documentation covers support for web applications designed to run on a traditional Servlet stack (Servlet API + Servlet container). Chapters cover the Servlet-based <<mvc,Spring MVC>> web framework including <<mvc-view,Views>>, <<mvc-cors,CORS>>, and <<websocket,WebSocket>> support. Note that as of Spring Framework 5.0 web applications can also run on a <<reactive-web.adoc#spring-reactive-web, reactive web stack>> (Reactive Streams API + non-blocking runtime). include::web/webmvc.adoc[leveloffset=+1] include::web/webmvc-view.adoc[leveloffset=+1] include::web/webmvc-cors.adoc[leveloffset=+1] include::web/websocket.adoc[leveloffset=+1]
Remove a comma in doc to make example a valid json.	[[mapping-dynamic-mapping]] == Dynamic Mapping Default mappings allow to automatically apply generic mapping definition to types that do not have mapping pre defined. This is mainly done thanks to the fact that the <<mapping-object-type,object mapping>> and namely the <<mapping-root-object-type,root object mapping>> allow for schema-less dynamic addition of unmapped fields. The default mapping definition is plain mapping definition that is embedded within the distribution: [source,js] -------------------------------------------------- { "_default_" : { } } -------------------------------------------------- Pretty short, no? Basically, everything is defaulted, especially the dynamic nature of the root object mapping. The default mapping definition can be overridden in several manners. The simplest manner is to simply define a file called `default-mapping.json` and placed it under the `config` directory (which can be configured to exist in a different location). It can also be explicitly set using the `index.mapper.default_mapping_location` setting. The dynamic creation of mappings for unmapped types can be completely disabled by setting `index.mapper.dynamic` to `false`. As an example, here is how we can change the default <<mapping-date-format,date_formats>> used in the root and inner object types: [source,js] -------------------------------------------------- { "_default_" : { "date_formats" : ["yyyy-MM-dd", "dd-MM-yyyy", "date_optional_time"], } } --------------------------------------------------	[[mapping-dynamic-mapping]] == Dynamic Mapping Default mappings allow to automatically apply generic mapping definition to types that do not have mapping pre defined. This is mainly done thanks to the fact that the <<mapping-object-type,object mapping>> and namely the <<mapping-root-object-type,root object mapping>> allow for schema-less dynamic addition of unmapped fields. The default mapping definition is plain mapping definition that is embedded within the distribution: [source,js] -------------------------------------------------- { "_default_" : { } } -------------------------------------------------- Pretty short, no? Basically, everything is defaulted, especially the dynamic nature of the root object mapping. The default mapping definition can be overridden in several manners. The simplest manner is to simply define a file called `default-mapping.json` and placed it under the `config` directory (which can be configured to exist in a different location). It can also be explicitly set using the `index.mapper.default_mapping_location` setting. The dynamic creation of mappings for unmapped types can be completely disabled by setting `index.mapper.dynamic` to `false`. As an example, here is how we can change the default <<mapping-date-format,date_formats>> used in the root and inner object types: [source,js] -------------------------------------------------- { "_default_" : { "date_formats" : ["yyyy-MM-dd", "dd-MM-yyyy", "date_optional_time"] } } --------------------------------------------------
Remove abbrevtitles for Asciidoctor migration	[[release-highlights]] = {es} Release Highlights ++++ <titleabbrev>Release Highlights</titleabbrev> ++++ [partintro] -- This section summarizes the most important changes in each release. For the full list, see <<es-release-notes>> and <<breaking-changes>>. * <<release-highlights-6.7.0>> * <<release-highlights-6.6.0>> * <<release-highlights-6.5.0>> * <<release-highlights-6.4.0>> * <<release-highlights-6.3.0>> -- include::highlights-6.7.0.asciidoc[] include::highlights-6.6.0.asciidoc[] include::highlights-6.5.0.asciidoc[] include::highlights-6.4.0.asciidoc[] include::highlights-6.3.0.asciidoc[]	[[release-highlights]] = Release Highlights [partintro] -- This section summarizes the most important changes in each release. For the full list, see <<es-release-notes>> and <<breaking-changes>>. * <<release-highlights-6.7.0>> * <<release-highlights-6.6.0>> * <<release-highlights-6.5.0>> * <<release-highlights-6.4.0>> * <<release-highlights-6.3.0>> -- include::highlights-6.7.0.asciidoc[] include::highlights-6.6.0.asciidoc[] include::highlights-6.5.0.asciidoc[] include::highlights-6.4.0.asciidoc[] include::highlights-6.3.0.asciidoc[]
Add note about link-local IP addresses	[id="understanding-networking"] = Understanding networking include::modules/common-attributes.adoc[] :context: understanding-networking toc::[] Kubernetes ensures that Pods are able to network with each other, and allocates each Pod an IP address from an internal network. This ensures all containers within the Pod behave as if they were on the same host. Giving each Pod its own IP address means that Pods can be treated like physical hosts or virtual machines in terms of port allocation, networking, naming, service discovery, load balancing, application configuration, and migration. include::modules/nw-ne-openshift-dns.adoc[leveloffset=+1]	[id="understanding-networking"] = Understanding networking include::modules/common-attributes.adoc[] :context: understanding-networking toc::[] Kubernetes ensures that Pods are able to network with each other, and allocates each Pod an IP address from an internal network. This ensures all containers within the Pod behave as if they were on the same host. Giving each Pod its own IP address means that Pods can be treated like physical hosts or virtual machines in terms of port allocation, networking, naming, service discovery, load balancing, application configuration, and migration. [NOTE] ==== Some cloud platforms offer metadata APIs that listen on the 169.254.169.254 IP address, a link-local IP address in the IPv4 `169.254.0.0/16` CIDR block. This CIDR block is not reachable from the pod network. Pods that need access to these IP addresses must be given host network access by setting the `spec.hostNetwork` field in the Pod spec to `true`. If you allow a Pod host network access, you grant the Pod privileged access to the underlying network infrastructure. ==== include::modules/nw-ne-openshift-dns.adoc[leveloffset=+1]
Update What's New for 6.0	[[new]] = What's New in Spring Security 6.0 Spring Security 6.0 provides a number of new features. Below are the highlights of the release. == Breaking Changes * https://github.com/spring-projects/spring-security/issues/10556[gh-10556] - Remove EOL OpenSaml 3 Support. Use the OpenSaml 4 Support instead. * https://github.com/spring-projects/spring-security/issues/8980[gh-8980] - Remove unsafe/deprecated `Encryptors.querableText(CharSequence,CharSequence)`. Instead use data storage to encrypt values. * https://github.com/spring-projects/spring-security/issues/11520[gh-11520] - Remember Me uses SHA256 by default * https://github.com/spring-projects/spring-security/issues/8819 - Move filters to web package Reorganize imports * https://github.com/spring-projects/spring-security/issues/7349 - Move filter and token to appropriate packages Reorganize imports * https://github.com/spring-projects/spring-security/issues/11026[gh-11026] - Use `RequestAttributeSecurityContextRepository` instead of `NullSecurityContextRepository`	[[new]] = What's New in Spring Security 6.0 Spring Security 6.0 provides a number of new features. Below are the highlights of the release. == Breaking Changes * https://github.com/spring-projects/spring-security/issues/10556[gh-10556] - Remove EOL OpenSaml 3 Support. Use the OpenSaml 4 Support instead. * https://github.com/spring-projects/spring-security/issues/8980[gh-8980] - Remove unsafe/deprecated `Encryptors.querableText(CharSequence,CharSequence)`. Instead use data storage to encrypt values. * https://github.com/spring-projects/spring-security/issues/11520[gh-11520] - Remember Me uses SHA256 by default * https://github.com/spring-projects/spring-security/issues/8819 - Move filters to web package Reorganize imports * https://github.com/spring-projects/spring-security/issues/7349 - Move filter and token to appropriate packages Reorganize imports * https://github.com/spring-projects/spring-security/issues/11026[gh-11026] - Use `RequestAttributeSecurityContextRepository` instead of `NullSecurityContextRepository` * https://github.com/spring-projects/spring-security/pull/11887[gh-11827] - Change default authority for `oauth2Login()`
Add note to etcd encryption section	// Module included in the following assemblies: // // * security/encrypting-etcd.adoc // * post_installation_configuration/cluster-tasks.adoc [id="about-etcd_{context}"] = About etcd encryption By default, etcd data is not encrypted in {product-title}. You can enable etcd encryption for your cluster to provide an additional layer of data security. For example, it can help protect the loss of sensitive data if an etcd backup is exposed to the incorrect parties. When you enable etcd encryption, the following OpenShift API server and Kubernetes API server resources are encrypted: * Secrets * Config maps * Routes * OAuth access tokens * OAuth authorize tokens When you enable etcd encryption, encryption keys are created. These keys are rotated on a weekly basis. You must have these keys to restore from an etcd backup.	// Module included in the following assemblies: // // * security/encrypting-etcd.adoc // * post_installation_configuration/cluster-tasks.adoc [id="about-etcd_{context}"] = About etcd encryption By default, etcd data is not encrypted in {product-title}. You can enable etcd encryption for your cluster to provide an additional layer of data security. For example, it can help protect the loss of sensitive data if an etcd backup is exposed to the incorrect parties. When you enable etcd encryption, the following OpenShift API server and Kubernetes API server resources are encrypted: * Secrets * Config maps * Routes * OAuth access tokens * OAuth authorize tokens When you enable etcd encryption, encryption keys are created. These keys are rotated on a weekly basis. You must have these keys to restore from an etcd backup. [NOTE] ==== Keep in mind that etcd encryption only encrypts values, not keys. This means that resource types, namespaces, and object names are unencrypted. ====
Fix link to milestone page	[[release-notes-5.7.0]] == 5.7.0 Date of Release: ❓ Scope: ❓ For a complete list of all _closed_ issues and pull requests for this release, consult the link:{junit5-repo}+/milestone/?closed=1+[5.7.0] milestone page in the JUnit repository on GitHub. [[release-notes-5.7.0-junit-platform]] === JUnit Platform ==== Bug Fixes * ❓ ==== Deprecations and Breaking Changes * ❓ ==== New Features and Improvements * ❓ [[release-notes-5.7.0-junit-jupiter]] === JUnit Jupiter ==== Bug Fixes * ❓ ==== Deprecations and Breaking Changes * ❓ ==== New Features and Improvements * ❓ [[release-notes-5.7.0-junit-vintage]] === JUnit Vintage ==== Bug Fixes * ❓ ==== Deprecations and Breaking Changes * ❓ ==== New Features and Improvements * ❓	[[release-notes-5.7.0]] == 5.7.0 Date of Release: ❓ Scope: ❓ For a complete list of all _closed_ issues and pull requests for this release, consult the link:{junit5-repo}+/milestone/50?closed=1+[5.7.0] milestone page in the JUnit repository on GitHub. [[release-notes-5.7.0-junit-platform]] === JUnit Platform ==== Bug Fixes * ❓ ==== Deprecations and Breaking Changes * ❓ ==== New Features and Improvements * ❓ [[release-notes-5.7.0-junit-jupiter]] === JUnit Jupiter ==== Bug Fixes * ❓ ==== Deprecations and Breaking Changes * ❓ ==== New Features and Improvements * ❓ [[release-notes-5.7.0-junit-vintage]] === JUnit Vintage ==== Bug Fixes * ❓ ==== Deprecations and Breaking Changes * ❓ ==== New Features and Improvements * ❓
Fix BibText reference (the author tag didn't didn't compile well in latex)	= Research :awestruct-description: Academic research for papers and articles. :awestruct-layout: normalBase :showtitle: OptaPlanner is a good base for metaheuristics research. Read about some of the advantages in http://www.orcomplete.com/research/geoffrey-de-smet/open-source-metaheuristics-research-on-drools-planner[this article]. Especially https://www.youtube.com/watch?v=JpcPEieU3Cg[OptaPlanner Benchmarker] and our big set of already implemented use cases, make it easy to test your new algorithm objectively against the existing algorithms. If you're doing academic or professional research on top of OptaPlanner, link:../community/team.html[let us know]. To reference OptaPlanner or the user manual, please use this BibTeX reference: ---- @manual{optaplanner, author = {Geoffrey De Smet et al}, title = {OptaPlanner User Guide}, organization = {Red Hat and the community}, url = {https://www.optaplanner.org}, note = {OptaPlanner is an open source constraint satisfaction solver in Java} } ----	= Research :awestruct-description: Academic research for papers and articles. :awestruct-layout: normalBase :showtitle: OptaPlanner is a good base for metaheuristics research. Read about some of the advantages in http://www.orcomplete.com/research/geoffrey-de-smet/open-source-metaheuristics-research-on-drools-planner[this article]. Especially https://www.youtube.com/watch?v=JpcPEieU3Cg[OptaPlanner Benchmarker] and our big set of already implemented use cases, make it easy to test your new algorithm objectively against the existing algorithms. If you're doing academic or professional research on top of OptaPlanner, link:../community/team.html[let us know]. To reference OptaPlanner or the user manual, please use this BibTeX reference: ---- @manual{optaplanner, author = {De Smet, Geoffrey and open source contributors}, title = {OptaPlanner User Guide}, year = {2006}, organization = {Red Hat, Inc. or third-party contributors}, url = {https://www.optaplanner.org}, note = {OptaPlanner is an open source constraint solver in Java} } ----
Add description to reload changes in poll-outages.xml	// Allow GitHub image rendering :imagesdir: ../../../images [[ga-opennms-operation-daemon-config-files-pollerd]] ==== Pollerd [options="header, autowidth"] \|=== \| Internal Daemon Name \| Reload Event \| _Pollerd_ \| `uei.opennms.org/internal/reloadDaemonConfig -p 'daemonName Pollerd'` \|=== .Pollerd configuration file overview [options="header, autowidth"] \|=== \| File \| Restart Required \| Reload Event \| Description \| `poller-configuration.xml` \| yes \| yes \| Restart is required in case new monitors are created or removed. Reload Event loads changed configuration parameters of existing monitors. \| `response-graph.properties` \| no \| no \| Graph definition for response time graphs from monitors \| `poll-outages.xml` \| ? \| ? \| ? \|===	// Allow GitHub image rendering :imagesdir: ../../../images [[ga-opennms-operation-daemon-config-files-pollerd]] ==== Pollerd [options="header, autowidth"] \|=== \| Internal Daemon Name \| Reload Event \| _Pollerd_ \| `uei.opennms.org/internal/reloadDaemonConfig -p 'daemonName Pollerd'` \|=== .Pollerd configuration file overview [options="header, autowidth"] \|=== \| File \| Restart Required \| Reload Event \| Description \| `poller-configuration.xml` \| yes \| yes \| Restart is required in case new monitors are created or removed. Reload Event loads changed configuration parameters of existing monitors. \| `response-graph.properties` \| no \| no \| Graph definition for response time graphs from monitors \| `poll-outages.xml` \| no \| yes \| Can be reloaded with `uei.opennms.org/internal/schedOutagesChanged` \|===
Introduce README and externalize common information via variables	= {project-name} - Using JWT RBAC This guide explains how your {project-name} application can utilize MicroProfile JWT RBAC to provide secured access to the JAX-RS endpoints. == TODO	= {project-name} - Using JWT RBAC This guide explains how your {project-name} application can utilize MicroProfile JWT RBAC to provide secured access to the JAX-RS endpoints. [cols="<m,<m,<2",options="header"] \|=== \|Property Name\|Default\|Description \|quarkus.jwt.enabled\|true\|Determine if the jwt extension is enabled. \|quarkus.jwt.realm-name\|Quarkus-JWT\|Name to use for security realm. \|quarkus.jwt.auth-mechanism\|MP-JWT\|Name to use for authentication mechanism \|=== == Solution We recommend that you follow the instructions in the next sections and create the application step by step. However, you can skip right to the completed example. Clone the Git repository: `git clone `, or download an {quickstart-url}/archive/master.zip[archive]. The solution is located in the `using-opentracing` {quickstart-url}[directory].
Remove references to changelog and to highlights	include::how-to.asciidoc[] include::testing.asciidoc[] include::glossary.asciidoc[] include::release-notes/highlights.asciidoc[] include::release-notes.asciidoc[]	include::how-to.asciidoc[] include::testing.asciidoc[] include::glossary.asciidoc[]
Align title with docs.asciidoctor.org site requirements	= Asciidoctor Maven User Manual The Asciidoctor Maven Plugin is the official way to convert your {uri-asciidoc}[AsciiDoc] documentation using {uri-asciidoctor}[Asciidoctor] from an {uri-maven}[Apache Maven] build. The project main goal is to offer a thin layer on top of https://github.com/asciidoctor/asciidoctorj[Asciidoctorj] following as much as possible to common Maven practices. The conversion can happen in 2 flavors: . As a xref:plugin:introduction.adoc[Maven plugin]: AsciiDoc files are converted at full Asciidoctor power independently from Maven site, . As a xref:plugin:introduction.adoc[Maven site module]: AsciiDoc files are integrated with https://maven.apache.org/doxia/[Maven Doxia] tools, however, with a few limitations.	= Asciidoctor Maven Tools Documentation :navtitle: Introduction The Asciidoctor Maven Plugin is the official way to convert your {uri-asciidoc}[AsciiDoc] documentation using {uri-asciidoctor}[Asciidoctor] from an {uri-maven}[Apache Maven] build. The project main goal is to offer a thin layer on top of https://github.com/asciidoctor/asciidoctorj[Asciidoctorj] following as much as possible to common Maven practices. The conversion can happen in 2 flavors: . As a xref:plugin:introduction.adoc[Maven plugin]: AsciiDoc files are converted at full Asciidoctor power independently from Maven site, . As a xref:plugin:introduction.adoc[Maven site module]: AsciiDoc files are integrated with https://maven.apache.org/doxia/[Maven Doxia] tools, however, with a few limitations.
Use the guides without toc layout	//// This guide is maintained in the main Quarkus repository and pull requests should be submitted there: https://github.com/quarkusio/quarkus/tree/master/docs/src/main/asciidoc //// = Quarkus - All configuration options include::./attributes.adoc[] include::{generated-dir}/config/all-config.adoc[opts=optional]	--- layout: guides-configuration-reference --- //// This guide is maintained in the main Quarkus repository and pull requests should be submitted there: https://github.com/quarkusio/quarkus/tree/master/docs/src/main/asciidoc //// = Quarkus - All configuration options include::./attributes.adoc[] include::{generated-dir}/config/all-config.adoc[opts=optional]
Update documentation version and date	= tick Malcolm Sparks <mal@juxt.pro>; Henry Widd; Johanna Antonelli <joa@juxt.pro> 0.4-1, 2018-02-09 :toc: left :toclevels: 4 :docinfo: shared :sectnums: true :sectnumlevels: 2 :xrefstyle: short :nofooter: :leveloffset: +1 include::intro.adoc[] include::setup.adoc[] include::api.adoc[] include::dates.adoc[] include::durations.adoc[] include::clocks.adoc[] include::intervals.adoc[] include::calendars.adoc[] include::schedules.adoc[] include::formatting.adoc[] include::cookbook/index.adoc[] include::bibliography.adoc[]	= tick Malcolm Sparks <mal@juxt.pro>; Henry Widd; Johanna Antonelli <joa@juxt.pro> 0.4.5-alpha, 2018-10-10 :toc: left :toclevels: 4 :docinfo: shared :sectnums: true :sectnumlevels: 2 :xrefstyle: short :nofooter: :leveloffset: +1 include::intro.adoc[] include::setup.adoc[] include::api.adoc[] include::dates.adoc[] include::durations.adoc[] include::clocks.adoc[] include::intervals.adoc[] include::calendars.adoc[] include::schedules.adoc[] include::formatting.adoc[] include::cookbook/index.adoc[] include::bibliography.adoc[]
Add docs for how to use the capsule command	= Creating an Uberjar Edge provides a script for running pack to build an uberjar. To use it, you can simply run the below from your project sub-directory (the same folder as your deps.edn). [source,shell] ---- $ ../bin/onejar -A:prod --args '-m edge.main' project.jar ---- The `-A:prod` indicates an alias you would like to have its `:extra-deps` and `:paths` included in your resulting jar. `--args` are default arguments to your jar, in this case we are specifying that the application should run edge.main, part of the edge production modules. You can run this jar in production quite easily: [source,shell] ---- $ java -Xmx1G -jar project.jar ---- We recommend that you specify the memory usage of your JVM, as the default on Java 6+ is usually insufficient for hosts run only this JVM process. A rule of thumb is to use 2/3rds of the memory of your host.	= Creating an Uberjar == OneJar Edge provides a script for running pack to build an uberjar. To use it, you can simply run the below from your project sub-directory (the same folder as your deps.edn). [source,shell] ---- $ ../bin/onejar -A:prod --args '-m edge.main' project.jar ---- The `-A:prod` indicates an alias you would like to have its `:extra-deps` and `:paths` included in your resulting jar. `--args` are default arguments to your jar, in this case we are specifying that the application should run edge.main, part of the edge production modules. == Capsule Build a capsule uberjar using this command: [source,shell] ---- $ ../bin/capsule -m edge.main -e 'target/prod' -A:prod project.jar ---- If you are using clojurescript in your project make sure you run this command first: [source,shell] ---- $ clojure -A:build:build/once ---- It will build the clojurescript files and put them in the correct folder to be included in the uberjar. == Running the jar You can run the produced jar in production quite easily: [source,shell] ---- $ java -Xmx1G -jar project.jar ---- We recommend that you specify the memory usage of your JVM, as the default on Java 6+ is usually insufficient for hosts run only this JVM process. A rule of thumb is to use 2/3rds of the memory of your host.
Remove legacy LaTeX math delimiters in latexmath:[]	// .basic [why]#chunky bacon# // .emphasis _chunky bacon_ // .emphasis-with-role [why]_chunky bacon_ // .strong chunky bacon // .strong-with-role [why]chunky bacon // .monospaced `hello world!` // .monospaced-with-role [why]`hello world!` // .superscript ^super^chunky bacon // .superscript-with-role [why]^super^chunky bacon // .subscript ~sub~chunky bacon // .subscript-with-role [why]~sub~chunky bacon // .mark #chunky bacon# // .double "`chunky bacon`" // .double-with-role [why]"`chunky bacon`" // .single '`chunky bacon`' // .single-with-role [why]'`chunky bacon`' // .asciimath asciimath:[sqrt(4) = 2] // .latexmath latexmath:[$C = \alpha + \beta Y^{\gamma} + \epsilon$] // .with-id [#why]_chunky bacon_ // .mixed-monospace-bold-italic `_monospace bold italic phrase_` and le``__tt__``ers	// .basic [why]#chunky bacon# // .emphasis _chunky bacon_ // .emphasis-with-role [why]_chunky bacon_ // .strong chunky bacon // .strong-with-role [why]chunky bacon // .monospaced `hello world!` // .monospaced-with-role [why]`hello world!` // .superscript ^super^chunky bacon // .superscript-with-role [why]^super^chunky bacon // .subscript ~sub~chunky bacon // .subscript-with-role [why]~sub~chunky bacon // .mark #chunky bacon# // .double "`chunky bacon`" // .double-with-role [why]"`chunky bacon`" // .single '`chunky bacon`' // .single-with-role [why]'`chunky bacon`' // .asciimath asciimath:[sqrt(4) = 2] // .latexmath latexmath:[C = \alpha + \beta Y^{\gamma} + \epsilon] // .with-id [#why]_chunky bacon_ // .mixed-monospace-bold-italic `_monospace bold italic phrase_` and le``__tt__``ers
Fix storage class CSI note in Creating SC-EBS/GCE	// Be sure to set the :StorageClass: and :Provisioner: value in each assembly // on the line before the include statement for this module. For example, to // set the StorageClass value to "AWS EBS", add the following line to the // assembly: // :StorageClass: AWS EBS // Module included in the following assemblies: // // * storage/persistent_storage-aws.adoc [id="storage-create-{StorageClass}-storage-class_{context}"] = Creating the {StorageClass} storage class Storage classes are used to differentiate and delineate storage levels and usages. By defining a storage class, users can obtain dynamically provisioned persistent volumes. .Procedure . In the {product-title} console, click Storage -> Storage Classes. . In the storage class overview, click Create Storage Class. . Define the desired options on the page that appears. .. Enter a name to reference the storage class. .. Enter an optional description. .. Select the reclaim policy. .. Select `{Provisioner}` from the drop down list. + [NOTE] ==== For Container Storage Interface (CSI) provisioning, select `ebs.csi.aws.com`. ==== .. Enter additional parameters for the storage class as desired. . Click Create to create the storage class. // Undefine {StorageClass} attribute, so that any mistakes are easily spotted :!StorageClass:	// Be sure to set the :StorageClass: and :Provisioner: value in each assembly // on the line before the include statement for this module. For example, to // set the StorageClass value to "AWS EBS", add the following line to the // assembly: // :StorageClass: AWS EBS // Module included in the following assemblies: // // * storage/persistent_storage-aws.adoc [id="storage-create-{StorageClass}-storage-class_{context}"] = Creating the {StorageClass} storage class Storage classes are used to differentiate and delineate storage levels and usages. By defining a storage class, users can obtain dynamically provisioned persistent volumes. .Procedure . In the {product-title} console, click Storage -> Storage Classes. . In the storage class overview, click Create Storage Class. . Define the desired options on the page that appears. .. Enter a name to reference the storage class. .. Enter an optional description. .. Select the reclaim policy. .. Select `{Provisioner}` from the drop down list. .. Enter additional parameters for the storage class as desired. . Click Create to create the storage class. // Undefine {StorageClass} attribute, so that any mistakes are easily spotted :!StorageClass:
Add Dave Syer to Authors	= Spring Security Reference Ben Alex; Luke Taylor; Rob Winch; Gunnar Hillert; Joe Grandja; Jay Bryant; Eddú Meléndez; Josh Cummings :include-dir: _includes :security-api-url: https://docs.spring.io/spring-security/site/docs/current/api/ :source-indent: 0 :tabsize: 4 :toc: left // FIXME: Add links for authentication, authorization, common attacks Spring Security is a framework that provides authentication, authorization, and protection against common attacks. // FIXME: Add links for imperative and reactive applications With first class support for both imperative and reactive applications, it is the de-facto standard for securing Spring-based applications. include::{include-dir}/about/index.adoc[] include::{include-dir}/servlet/index.adoc[] include::{include-dir}/reactive/index.adoc[]	= Spring Security Reference Ben Alex; Luke Taylor; Rob Winch; Gunnar Hillert; Joe Grandja; Jay Bryant; Eddú Meléndez; Josh Cummings; Dave Syer :include-dir: _includes :security-api-url: https://docs.spring.io/spring-security/site/docs/current/api/ :source-indent: 0 :tabsize: 4 :toc: left // FIXME: Add links for authentication, authorization, common attacks Spring Security is a framework that provides authentication, authorization, and protection against common attacks. // FIXME: Add links for imperative and reactive applications With first class support for both imperative and reactive applications, it is the de-facto standard for securing Spring-based applications. include::{include-dir}/about/index.adoc[] include::{include-dir}/servlet/index.adoc[] include::{include-dir}/reactive/index.adoc[]
Include REST API docs that were already produced.	[[rest-api-node-properties]] == Node properties == include::set-property-on-node.asciidoc[] include::update-node-properties.asciidoc[] include::get-properties-for-node.asciidoc[] include::property-values-can-not-be-null.asciidoc[] include::property-values-can-not-be-nested.asciidoc[] include::delete-all-properties-from-node.asciidoc[] include::delete-a-named-property-from-a-node.asciidoc[]	[[rest-api-node-properties]] == Node properties == include::set-property-on-node.asciidoc[] include::update-node-properties.asciidoc[] include::get-properties-for-node.asciidoc[] include::get-property-for-node.asciidoc[] include::property-values-can-not-be-null.asciidoc[] include::property-values-can-not-be-nested.asciidoc[] include::delete-all-properties-from-node.asciidoc[] include::delete-a-named-property-from-a-node.asciidoc[]
Include shared/attributes.asciidoc directly from docs master	[[elasticsearch-reference]] = Elasticsearch Reference :include-xpack: true :xes-repo-dir: {docdir} :es-repo-dir: {docdir}/../../../../elasticsearch/docs :es-test-dir: {docdir}/../../../../elasticsearch/docs/src/test :plugins-examples-dir: {docdir}/../../../../elasticsearch/plugins/examples :docs-dir: {docdir}/../../../../docs include::{es-repo-dir}/Versions.asciidoc[] include::{es-repo-dir}/reference/index-shared1.asciidoc[] :edit_url!: include::setup-xes.asciidoc[] :edit_url: include::{es-repo-dir}/reference/index-shared2.asciidoc[] :edit_url!: include::rest-api/index.asciidoc[] :edit_url: include::{es-repo-dir}/reference/index-shared3.asciidoc[]	[[elasticsearch-reference]] = Elasticsearch Reference :include-xpack: true :xes-repo-dir: {docdir} :es-repo-dir: {docdir}/../../../../elasticsearch/docs :es-test-dir: {docdir}/../../../../elasticsearch/docs/src/test :plugins-examples-dir: {docdir}/../../../../elasticsearch/plugins/examples include::{es-repo-dir}/Versions.asciidoc[] include::{es-repo-dir}/reference/index-shared1.asciidoc[] :edit_url!: include::setup-xes.asciidoc[] :edit_url: include::{es-repo-dir}/reference/index-shared2.asciidoc[] :edit_url!: include::rest-api/index.asciidoc[] :edit_url: include::{es-repo-dir}/reference/index-shared3.asciidoc[]
Fix Java API documentation for indexed scripts	[[indexed-scripts]] == Indexed Scripts API The indexed script API allows one to interact with scripts and templates stored in an elasticsearch index. It can be used to create, update, get, and delete indexed scripts and templates. [source,java] -------------------------------------------------- PutIndexedScriptResponse = client.preparePutIndexedScript() .setScriptLang("groovy") .setId("script1") .setSource("_score * doc['my_numeric_field'].value") .execute() .actionGet(); GetIndexedScriptResponse = client.prepareGetIndexedScript() .setScriptLang("groovy") .setId("script1") .execute() .actionGet(); DeleteIndexedScriptResponse = client.prepareDeleteIndexedScript() .setScriptLang("groovy") .setId("script1") .execute() .actionGet(); -------------------------------------------------- To store templates simply use "mustache" for the scriptLang. === Script Language The API allows one to set the language of the indexed script being interacted with. If one is not provided the default scripting language will be used.	[[indexed-scripts]] == Indexed Scripts API The indexed script API allows one to interact with scripts and templates stored in an elasticsearch index. It can be used to create, update, get, and delete indexed scripts and templates. [source,java] -------------------------------------------------- PutIndexedScriptResponse = client.preparePutIndexedScript() .setScriptLang("groovy") .setId("script1") .setSource("script", "_score * doc['my_numeric_field'].value") .execute() .actionGet(); GetIndexedScriptResponse = client.prepareGetIndexedScript() .setScriptLang("groovy") .setId("script1") .execute() .actionGet(); DeleteIndexedScriptResponse = client.prepareDeleteIndexedScript() .setScriptLang("groovy") .setId("script1") .execute() .actionGet(); -------------------------------------------------- To store templates simply use "mustache" for the scriptLang. === Script Language The API allows one to set the language of the indexed script being interacted with. If one is not provided the default scripting language will be used.
Add Link to DispatcherServlet in Filter Review Doc	[[servlet-filters-review]] = A Review of ``Filter``s Spring Security's Servlet support is based on Servlet ``Filter``s, so it is helpful to look at the role of ``Filter``s generally first. The picture below shows the typical layering of the handlers for a single HTTP request. .FilterChain [[servlet-filterchain-figure]] image::{figures}/filterchain.png[] The client sends a request to the application, and the container creates a `FilterChain` which contains the ``Filter``s and `Servlet` that should process the `HttpServletRequest` based on the path of the request URI. At most one `Servlet` can handle a single `HttpServletRequest` and `HttpServletResponse`. However, more than one `Filter` can be used to: * Prevent downstream ``Filter``s or the `Servlet` from being invoked. In this instance the `Filter` will typically write the `HttpServletResponse`. * Modify the `HttpServletRequest` or `HttpServletResponse` used by the downstream ``Filter``s and `Servlet` The power of the `Filter` comes from the `FilterChain` that is passed into it. .`FilterChain` Usage Example === [source,java] ---- public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) { // do something before the rest of the application chain.doFilter(request, response); // invoke the rest of the application // do something after the rest of the application } ---- === Since a `Filter` only impacts downstream ``Filter``s and the `Servlet`, the order each `Filter` is invoked is extremely important.	[[servlet-filters-review]] = A Review of ``Filter``s Spring Security's Servlet support is based on Servlet ``Filter``s, so it is helpful to look at the role of ``Filter``s generally first. The picture below shows the typical layering of the handlers for a single HTTP request. .FilterChain [[servlet-filterchain-figure]] image::{figures}/filterchain.png[] The client sends a request to the application, and the container creates a `FilterChain` which contains the ``Filter``s and `Servlet` that should process the `HttpServletRequest` based on the path of the request URI. In a Spring MVC application the `Servlet` is an instance of https://docs.spring.io/spring-security/site/docs/current-SNAPSHOT/reference/html5/#servlet-filters-review[`DispatcherServlet`]. At most one `Servlet` can handle a single `HttpServletRequest` and `HttpServletResponse`. However, more than one `Filter` can be used to: * Prevent downstream ``Filter``s or the `Servlet` from being invoked. In this instance the `Filter` will typically write the `HttpServletResponse`. * Modify the `HttpServletRequest` or `HttpServletResponse` used by the downstream ``Filter``s and `Servlet` The power of the `Filter` comes from the `FilterChain` that is passed into it. .`FilterChain` Usage Example === [source,java] ---- public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) { // do something before the rest of the application chain.doFilter(request, response); // invoke the rest of the application // do something after the rest of the application } ---- === Since a `Filter` only impacts downstream ``Filter``s and the `Servlet`, the order each `Filter` is invoked is extremely important.
Add Eleftheria Stein to Reference Authors	= Spring Security Reference Ben Alex; Luke Taylor; Rob Winch; Gunnar Hillert; Joe Grandja; Jay Bryant; Eddú Meléndez; Josh Cummings; Dave Syer :include-dir: _includes :security-api-url: https://docs.spring.io/spring-security/site/docs/current/api/ :source-indent: 0 :tabsize: 4 :toc: left // FIXME: Add links for authentication, authorization, common attacks Spring Security is a framework that provides authentication, authorization, and protection against common attacks. // FIXME: Add links for imperative and reactive applications With first class support for both imperative and reactive applications, it is the de-facto standard for securing Spring-based applications. include::{include-dir}/about/index.adoc[] include::{include-dir}/servlet/index.adoc[] include::{include-dir}/reactive/index.adoc[]	= Spring Security Reference Ben Alex; Luke Taylor; Rob Winch; Gunnar Hillert; Joe Grandja; Jay Bryant; Eddú Meléndez; Josh Cummings; Dave Syer; Eleftheria Stein :include-dir: _includes :security-api-url: https://docs.spring.io/spring-security/site/docs/current/api/ :source-indent: 0 :tabsize: 4 :toc: left // FIXME: Add links for authentication, authorization, common attacks Spring Security is a framework that provides authentication, authorization, and protection against common attacks. // FIXME: Add links for imperative and reactive applications With first class support for both imperative and reactive applications, it is the de-facto standard for securing Spring-based applications. include::{include-dir}/about/index.adoc[] include::{include-dir}/servlet/index.adoc[] include::{include-dir}/reactive/index.adoc[]