blacksmith-community / blacksmith-boshrelease Goto Github PK

Set up a saferc for targeting the local vault.

This BOSH release needs smoke tests.

Those smoke tests will need to:

1. Validate that the broker /v2/catalog endpoint loads
2. Validate that (if enabled) the management UI loads (no need to test js, just the / endpoint)
3. Defer to the errands for each colocated Blacksmith Forge release, to serially run tests on a per-service or per-plan basis.

Drop the helper stuff and boilerplate bosh-gen bits. Welcome to (almost) 2019!

We shouldn't need it, but ~vcap/.vault-token would be a good thing to have, and can be set up by the BOSH release scripts.

On a blacksmith node, ran safe -v. It said 0.0.7. I couldn't believe so I ran it five more times. It kept saying 0.0.7. This is wrong. This is bad. Let's fix it.

Deployment run with the four forges, PSQL, MariaDB, Redis, RabbitMQ, then one was removed, on the next deploy, the artifacts for that forge was left in the cache and stayed in the catalog.

Need to look at possibly flushing the cache on deploy to ensure full rebuild of the catalog

We've recently had this same issue crop up in blacksmith.log in a couple of different environments where blacksmith is registered as a service broker with Cloud Foundry:

2019/08/12 13:56:29 Error requesting deployments  Get https://10.188.30.100:25555/deployments: oauth2: cannot fetch token: 401
Response: {"error":"invalid_token","error_description":"The token has been revoked: 0190f0c71b08458b896adbc2e842271b-r"}
2019-08-12 13:56:29.463 INFO   [*] taskid for the bosh cleanup is 0
2019-08-12 13:56:29.463 ERROR  [*] bosh cleanup failed to run properly: Post https://10.188.30.100:25555/cleanup: oauth2: cannot fetch token: 401
Response: {"error":"invalid_token","error_description":"The token has been revoked: 0190f0c71b08458b896adbc2e842271b-r"}
wait_pid 3817 1 25 1 250

In both cases, we investigated after a developer complained they were unable to cf create-service, and on both occasions I temporarily resolved the issue with a bosh restart. It would be great if blacksmith checked itself whether its token is expired, and then sought a new as required.

The configuration file is not used. Remove it from the config file template.