feat(provider/cf): add provider skeleton with credentials management

[jkschneider]

Based on a conversation with @duftler, we're splitting up the Cloud Foundry provider submission into individual PRs that can be reviewed in smaller chunks.

This initial PR contains the skeleton of the provider, up to and including credentials.

cloudfoundry:
  enabled: true
  accounts:
    - name: pivotalwebservices
      user: MYUSER
      password: MYPASSWORD
      api: api.run.pivotal.io

cc / @ethanfrogers

[spinnakerbot]

The following commits need their title changed:

e833e31: feat(provider/cf) add provider skeleton with credentials management

Please format your commit title into the form:

<type>(<scope>): <subject>, e.g. fix(kubernetes): address NPE in status check

This allows us to easily generate changelogs & determine semantic version numbers when cutting releases. You can read more about commit conventions here.

[lwander]

👍

[lwander]

We try to write all new code in Java/Kotlin -- take for example the new k8s provider in clouddriver

It's not exactly a hard requirement, but would be nice

[jkschneider]

Oh boy. I wish we had known this before we wrote the whole provider.

[duftler]

There are some notes on the site here (https://www.spinnaker.io/community/contributing/back-end-code/), but we could definitely do a better job of publicizing this.

[jkschneider]

Frankly, we could probably put a little bit in the parent build to disallow it from even happening for new providers. But I suppose new providers don't come along every day.

[duftler]

We were thinking of adding it as a spinbot check.

[lwander]

We try to avoid eliding return

[lwander]

Same return comment here

[jkschneider]

@lwander @duftler converted to Java.

[lwander]

Awesome, sorry about the trouble

[duftler]

Nice!