SpringCloud/spring-cloud-cloudfoundry
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
254 Commits 12 Branches 0 Tags
76ca08222e193a1689e95cdca941a2f2180f091e
Commit Graph

7 Commits

Author SHA1 Message Date
Spring Operator
f1beab8475 URL Cleanup (#41) 
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# Fixed URLs

## Fixed Success 
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* [ ] http://www.apache.org/licenses/ with 1 occurrences migrated to:  
  https://www.apache.org/licenses/ ([https](https://www.apache.org/licenses/) result 200).
* [ ] http://www.apache.org/licenses/LICENSE-2.0 with 25 occurrences migrated to:  
  https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200).
 2019-04-01 11:34:35 -04:00
Marcin Grzejszczak
004e83b1e8 Added checkstyle 2019-02-05 15:21:41 +01:00
Scott Frederick
510b6ebcfc Improve Cloud Foundry Java Client auto-configuration. 
An organization and space are not required by all CF Java Client operations. Those properties should be optional to the client-autoconfiguration.

The CF target URL should default to the CF an application is running on when it is deployed to CF.
 2018-04-09 17:11:33 -05:00
Spencer Gibb
d275b72569 Add or update license headers 2018-01-09 15:21:52 -05:00
Spencer Gibb
3cb69505e3 polish 2018-01-08 17:08:13 -05:00
Spencer Gibb
673679fd00 Formatting 2018-01-08 16:55:33 -05:00
Josh Long
fef7d2c9a7 support Reactor-based CF Java Client (#22) 
* reactive Cloud Foundry Java Client

- new support for auto-configuring the reactor-based CF java client v3.3.
- reworkd the `DiscoveryClient` to depend on the standalone support.
- made the tests run conditionally based on presence of certain env vars.

fixes gh-21
 2018-01-08 16:45:02 -05:00