Jakob Fels

While building the reproducer I noticed that the problem is caused by including `spring-cloud-gcp-starter-data-firestore`, with plain data-jpa I could not reproduce it as well. I'll open an issue on that...

I opened a corresponding issue in the spring cloud gcp project: https://github.com/GoogleCloudPlatform/spring-cloud-gcp/issues/1113

Is there anything that can be contributed? Turning up some debug logging, it seems that jbang-shrinkwrap is not sending any additional headers when resolving a jar from a private gitlab...

It will not work. I'm using jbang 0.98.0 and during dependency resolution, gitlab authentication headers defined in ~/.m2/settings.xml will not be respected, resulting in no dependencies being pulled from the...

They don't use basic auth (username/password) but instead rely on custom headers (see https://github.com/jbangdev/jbang/issues/1077#issuecomment-968248365). I did some more digging, the issue seems to be how the dependency resolver is set...

Does not work for me, I'll comment on the PR

It seems like a similar issue was fixed for `create-service` in [v8.3.0](https://github.com/cloudfoundry/cli/releases/tag/v8.3.0) https://github.com/cloudfoundry/cli/commit/2b4e14408be4e571fdb95ebbf4065433c5f10efe

A workaround is to add `services: ((services))` to your manifest and the use `cf push --var services=[]` for no services and `--var services=[service1,service2]` to add services.