The Spring Boot 2.1.x ManagementWebSecurityConfigurerAdapter opens the health and info entry points by default.
Since those are sufficient for allowing SCDF server to manage the monitor the SCSt apps, there is no need to disable the entire security by excluding SecurityAutoConfiguration

Affects: spring-cloud-stream-app-maven-plugin

The README at the root of this meta-repo should explain what spring-cloud-stream-app-maven-plugin does, given it's the most important plugin!

Hello,
I want to use spring-cloud-app-starter-metadata-gradle-plugin (https://github.com/spring-cloud/spring-cloud-app-starters-maven-plugins/tree/master/spring-cloud-app-starter-metadata-gradle-plugin).
However I can't find the appropriate dependency in maven repository.

Related to spring-cloud/stream-applications#93

We need to upgrade the maven-surefire-plugin used in the generated apps to be 2.21.0. Without this, the tests are not run.

This is not on par with https://github.com/spring-cloud/spring-cloud-stream-app-starters/blob/master/spring-cloud-stream-app-documentation-maven-plugin/src/main/java/org/springframework/cloud/stream/app/documentation/plugin/ConfigurationMetadataDocumentationMojo.java

Move the doc maven plugin to a sub-directory
Add the metadata aggregator plugin as a sibling

Eventually, rename this repo

Currently a user that creates a starter application has no way of inserting properties into the application.properties that was created when the run -PgenerateApps . We need to be able to support this.

Currently the spring-cloud-stream-app-maven-plugin implementation relies on heavy and outdated libraries such as Spring Initializer and Plexus to generate the Stream Application projects.
Because of this the source code has overtime has become unmanageable and hardly testable.

The 2.x branch allows us to streamline and refactor the plugin implementation and remove all redundant, outdated dependencies.

Hello, @sobychacko!
I want to use spring-cloud-app-starter-metadata-gradle-plugin. However the id doesn't seem to work.

As a developer, I'd like to add and enable /actuator/info and /actuator/health endpoints to all 2.0 Apps.

Acceptance:
Include management.endpoints.web.exposure.include=health,info,bindings as a property to all the Apps.

Apps will provide a new dataflow specific whitelist properties file: dataflow-configuration-metadata-whitelist.properties. Use this file in the metadata generation if it is available, otherwise fall back to the old file name (spring-configuration-metadata-whitelist.properties).

See discussion at spring-attic/app-starters-release#99 (comment)

Hello
Is there the gradle plugin that creates the metadata jar with aggregated META-INF/spring-configuration-metadata.json file ?
Thanks

Please set up the CI to build and publish the gradle plugin, see PR #22. Worth to add few words in SCDF documentation as well once the plugin is published.

related to spring-cloud/stream-applications#94

As we explore the idea of replacing SCDF's app registry with container registry, it'd be useful to introspect and derive "application type" at the build phase, and add that to the "spring-configuration-metadata-encoded.properties" automatically.

SCDF can use this to present the type in its lightweight registry. Likewise, allow the SCDF DSL to do its thing.

As part of the generation process, the ``spring-cloud-stream-app-maven-plugin` generates Docker/Oci maven plugin configurations in the target App's POMs, used to build the Stream/Task Container Images.

The Docker/OCI image specification allows to include optional metadata to the build images using the configuration.

As a developer i would like to store the Apps metadata (produced by the metadata plugin) into the container's image configuration.

App generator POM should find out container level dependencies.

Currently the Metadata Plugin gathers all Boot metadata found on the filesystem or the classpath, merges it together and wraps it into a dedicated metadata jar.

As software developer i would like to be able to serialize a pre-selected subset of the detected metadata into an easy to access Java property file. This would allow me to reuse this selected metadata with other maven plugins or build tools.

• Make this functionality optional and configurable with Mojo parameters.
• Th metadata should be filterable by ItemMetadata#SourceType and ItemMetadata#Name filters.

This optional support would come handy for applications that simulate real-time activities such as the image-viewer-sink.

Currently, whitelist.properties are overridden by the last one loaded.

The README references the old architecture.

But more importantly, how do I build uberjars with the new approach?

Related to spring-cloud/stream-applications#93

Now that the metadata files come from the metadata artifact (which only has the metadata json files, and no .class files) it is impossible to get hints for enum values using reflection at runtime.

We should use the plugin as an opportunity to gather those (while classes are available) and convert them to hints in the json format

From @snicoll on May 4, 2018 13:53

The Spring Boot configuration metadata has the notion of deprecation with a level that can have two values:

• WARNING (default): the property is managed in a deprecated way and will be removed in a future release
• ERROR: the property is no longer managed and won't be honoured

The latter is a way to keep a reference to a key that used to work so that IDE can show an appropriate error and provide a migration strategy, if any.

If I go to the detail of a task in the UI, I will see those keys that are no longer supported. The UI should not display those at all as setting a value will have no effect. Of course, the side effect of that is that you shouldn't be able to set a value in the job definition either.

Copied from original issue: spring-cloud/spring-cloud-dataflow-ui#768

As we march towards replacing the app registry in SCDF with container registry proper, let's take the opportunity to deprecate "spring-cloud-app-starter-metadata-maven-plugin" and rename it to "spring-cloud-dataflow-app-plugin".