Hello Daniel, 

Thanks for your feedback. I have run the `gradle clean` and `gradle assemble`, but unfortunately, after that, the issue still exist. Is there any more ideas? It is important for our customers and us, I am looking forward to your help eagerly. Thanks for in advance.

Thanks and warm regards

Guimin, He

Dear Cloud Foundry Community,

I am Alibaba Cloud developer and I am working on integrating Alibaba Cloud with CloudFoundry. Now, I happened an issue when I deploy app spring-music: https://github.com/cloudfoundry-samples/spring-music, and I need your help.

The issue as following:

when I run command cf push to deploy spring-music firstly, it can be deployed successfully;

when I run command cf push again, it throw many warnings, as following:

Staging app and tracing logs...
   Downloading binary_buildpack...
   Downloading staticfile_buildpack...
   Downloading java_buildpack...
   Downloading ruby_buildpack...
   Downloaded ruby_buildpack
   Downloading dotnet_core_buildpack...
   Downloaded staticfile_buildpack
   Downloading nodejs_buildpack...
   Downloaded java_buildpack
   Downloading go_buildpack...
   Downloaded binary_buildpack
   Downloading python_buildpack...
   Downloaded nodejs_buildpack
   Downloading php_buildpack...
   Downloaded dotnet_core_buildpack
   Downloading nginx_buildpack...
   Downloaded go_buildpack
   Downloading r_buildpack...
   Downloaded python_buildpack
   Downloaded r_buildpack
   Downloaded nginx_buildpack
   Downloaded php_buildpack
   Cell ae633763-c016-4a05-90c3-89494ac040e7 creating container for instance 700500a8-5455-4bba-b438-116f09231b82
   Cell ae633763-c016-4a05-90c3-89494ac040e7 successfully created container for instance 700500a8-5455-4bba-b438-116f09231b82
   Downloading app package...
   Downloading build artifacts cache...
   Downloaded build artifacts cache (42.1M)
   Downloaded app package (62.4M)
   warning [/tmp/app/BOOT-INF/lib/spring-web-5.0.5.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/hibernate-core-5.2.16.Final.jar]:  6291456 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/jackson-databind-2.9.5.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-data-commons-2.0.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-data-mongodb-2.0.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-boot-autoconfigure-2.0.1.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/lettuce-core-5.0.3.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/aspectjweaver-1.8.13.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-context-5.0.5.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/h2-1.4.197.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-cloud-cloudfoundry-connector-2.0.1.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/hibernate-validator-6.0.9.Final.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/tomcat-embed-core-8.5.29.jar]:  2097152 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-data-redis-2.0.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/reactor-core-3.1.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/mongodb-driver-core-3.6.3.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-web-5.0.5.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/hibernate-core-5.2.16.Final.jar]:  6291456 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/jackson-databind-2.9.5.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-data-commons-2.0.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-data-mongodb-2.0.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-boot-autoconfigure-2.0.1.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/lettuce-core-5.0.3.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/aspectjweaver-1.8.13.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-context-5.0.5.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/h2-1.4.197.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-cloud-cloudfoundry-connector-2.0.1.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/hibernate-validator-6.0.9.Final.jar]:  1048576 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/tomcat-embed-core-8.5.29.jar]:  2097152 extra bytes at beginning or within zipfile
     (attempting to process anyway)
   warning [/tmp/app/BOOT-INF/lib/spring-data-redis-2.0.6.RELEASE.jar]:  1048576 extra bytes at beginning or within zipfile

My cf cli version is  6.51.0+2acd15650.2020-04-07.

In addition, about this issue, I have asked help in several days ago by slack cf-deployment channel: https://cloudfoundry.slack.com/archives/C2U7KA7M4/p1586335015016800 and capi channel: https://cloudfoundry.slack.com/archives/C07C04W4Q/p1586480456093000 , but there are no any reply.

Looking forward to your help.

Thanks and warm regards

Guimin, He

Dear Cloud Foundry Community,

Over the last year, we have seen the industry shift towards deploying software on top of Kubernetes. As a result, we have all chosen to invest heavily in building on top of Kubernetes. Separately, we have also observed that BOSH has reached a point of stability and maturity, such that there aren’t lots of incoming feature requests and enhancements to add.

We continue to view BOSH as an important project and are still fully committed to supporting our OSS users using BOSH for the next couple years . However, in light of these changes, several BOSH PMC projects[1] will be shifting from the pairing model to the distributed committer model (for more information about distributed committer vs pairing models, see the CFF Development Operations Policy [2], section IV.B.). Shatarupa Nandi (snandi@..., @rupa on CFF Slack) and Nadja Conklin (nconklin@..., @Nadja Conklin on CFF Slack) will temporarily step in as Project Leads. 

We are moving away from having a full time team working on each of the projects. Instead, we will have 6-8 engineers who will dedicate a portion of their time on a regular basis for ongoing support and maintenance of the BOSH projects. This will likely result in the following changes:

• A reduced cadence of cutting new stemcells and patching existing stemcells for low and medium severity CVEs. Presently, we aim to cut new stemcell patches every 2 weeks. We will now be doing the same every 6 weeks. We will maintain the status quo for high and critical CVEs and will patch those as soon as possible.

• We will pause working on Bionic stemcells and will not be cutting a new line of Bionic stemcells. We are aware that Xenial stemcells are supported until April 2021. This is an area where we are seeking help from the CFF community. Please see the end of the email. We may pick up this work during the 2nd half of the year, depending on cf-for-k8s adoption and our level of staffing on BOSH.

• A reduced cadence of new releases of BOSH PMC projects[1]. Since there will be little active development, we will move to cutting releases ad-hoc when there are enough changes built up.

• We will pause active development on the various CPIs (including OpenStack CPI, Azure CPI, GCP CPI, and AWS CPI.) We will continue to patch critical bugs, backwards incompatible IaaS API changes, and high severity CVEs. However, we will not be adding features to extend the capabilities of the CPIs.

• While we will continue to answer questions about BOSH, we will likely be less responsive than before. We still hope to answer questions on these Slack channels within a reasonable time. We will be most active in #bosh. Other BOSH Slack channels (for example, #bosh-core-dev) will see reduced activity and will be deprecated over time.

• The committers are all on cf-bosh@..., and will continue to engage with the community of users and contributors via the mailing lists. 

We would like to seek help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects. Here are some ways in which you can help us:

• Please help your friends in the community by answering questions on #bosh

• If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

• If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

• If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

• If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.

Thank you for your help and support!

[1] This includes the following repos: bosh, bosh-agent, bosh-dns-release, bosh-linux-stemcell-builder, bosh-deployment, bosh-cli, bbl, bosh.io github org, docs-bosh, bpm-release, bosh-google-cpi-release, bosh-azure-cpi-release, bosh-openstack-cpi-release, bosh-aws-cpi-release, bosh-lite, bosh-utils, bosh-s3cli, bosh-acceptance-tests, jumpbox-deployment, os-conf-release.

[2] https://www.cloudfoundry.org/wp-content/uploads/2017/01/CFF-DEV-OPS-POLICY.pdf

Cloud Foundry Community,

First and foremost, I truly hope that each of you is doing as well as can be expected in these extraordinary times.

As you may have seen, we announced a leadership change this morning. I am stepping into the role of Executive Director of the Cloud Foundry Foundation. Abby Kearns has accepted an executive role with another organization, to be announced. This is a very exciting opportunity for Abby, and all of us on the foundation’s staff and directors are extremely happy for her. Abby has been leading the foundation for several years through quite a bit of change in our project, our community, and the broader market. She’s not going far, but she will be missed.

We also announced that Paul Fazzone, SVP Tanzu R&D at VMware, has been elected to chair the board of directors. Paul has been a strong advocate and supporter of the foundation, having served as Treasurer for the foundation and as a director for several years now. Paul is taking over the role of chair from John Roese, who has been a steady hand from the organization’s inception. I am looking forward to working much more closely with Paul as we push the organization forward into the future. 

Our focus as a community has always been to make developers’ lives easier, and each of you has played a part in the long list of user success stories. Even today, as society grapples with the incredible challenge of a global pandemic, I am reminded of the incredible value of the work this community does. Organizations from around the world that have adopted Cloud Foundry are using it to respond in these trying times, each in their own way. National governments have used the Cloud Foundry platform to rapidly build, deploy and scale software that is helping their citizens get information and register for economic support. Countless corporations are using Cloud Foundry to both support their customers in new ways and do their part for the greater good. These responses have required actions measured in days and hours, not weeks and months. In short, this community’s efforts over the years have built something worthing being truly proud of.

This community is also one that has managed to continuously evolve the architecture of the platform through several major cycles of change. Today is no different, as we have come together on the shared mission of bringing the Cloud Foundry developer experience to Kubernetes clusters everywhere. 

As the ancient Greek philosopher, Heraclitus said, “Change is the only constant in life.” Our community embraces that way of thinking, both for the Cloud Foundry project itself and when considering how to continue to enhance the developer experience provided by the platform. Ultimately, the core Cloud Foundry function cf-push will remain well into the future, and its architecture will continue to evolve.

I’m sure many of you have questions about these changes, and I welcome the opportunity to answer them. Feel free to email me directly ( cchilders@... ), or join us for a slack-based AMA this Thursday, April 8th, from 8-10 AM PST on the Cloud Foundry community’s slack instance in the #cff-forum channel. I will be happy to discuss the transition, the future of the Foundation and respond to any comments or questions you may have.

-chip

Chip Childers

Executive Director

Cloud Foundry Foundation

I am using concourse v4.2.1 deployed using bosh on AWS.

When I hit the API endpoint /api/v1/info (in Postman, with Basic auth), I am able to get the response as below

{
    "version": "4.2.1",
    "worker_version": "2.1"
}

When I try to hit the API endpoint /api/v1/teams (in Postman, with Basic auth), I am getting Status 200 OK with an empty response like below.

[]

I am able to see the teams using fly command or also in the web UI, but not through API.

• Should I enable basic authentication for hitting API endpoints of concourse?
• Why am I not able to list the teams in concourse using the API /api/v1/teams? What am I missing?

---

Additional Info:

Referred to this concourse-bosh-deployment github repo for deploying concourse.

The sample command used to deploy concourse is given below:

bosh -e boshconcoursedir deploy -d boshconcourse concourse.yml \
  -l ../versions.yml \
  --vars-store cluster-creds.yml  \
  -o operations/static-web.yml  \
  --var web_ip=<<REDACTED>>   \
  --var network_name=default  \
  --var web_vm_type=<<REDACTED>>  \
  --var db_vm_type=<<REDACTED>>   \
  --var db_persistent_disk_type=<<REDACTED>> \
   --var worker_vm_type=<<REDACTED>> \
    --var deployment_name=boshconcourse \
    --var external_url=https://<<REDACTED>> \
    -o operations/add-local-users.yml \
    --var main_team_local_users=[admin] \
    --var add_local_users=[admin:<<REDACTED>>,myid@...:<<REDACTED>>]

Today I added the below line to the deployment command and deployed again, and still failed to get the teams from the API

  -o operations/basic-auth.yml \

After logging in as admin in fly, I am able to list the teams as below.

fly -t admin login -c https://something.com -u admin -p <<REDACTED>>
logging in to team 'main'


target saved

fly -t admin teams
name
team-1 
team-2
main 

I am not sure if this is the right place to ask this issue. Sorry if it is not. (Also posted a similar question in StackOverflow). Kindly assist me in resolving this issue.

Regards,
Arut