Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update articles in prompt_for database #142

Closed

Conversation

7hunderbird
Copy link

Propose a user experience small change. Could be helpful to visually grock.

rkoster and others added 30 commits February 5, 2020 16:04
* Bump to cf-deployment v12.25.0

* Also update buildpacks
The dev/update tool was moved to the devtools directory and renamed with
a more descriptive name.  It also contains a check for the dependency of
cf-deployment repo in the same parent directory as this kit.
The intention is that as of v2.0.0 of this kit, it will wrap the
community-supported `cf-deployment` de facto standard distribution.  The
final versions of v1.x will progressively move existing deployments
towards v2.0.0 so that it will be a no-op to deploy it.
- created uaa client for app-autoscaler as per [usage instructions](https://github.com/cloudfoundry/app-autoscaler-release/blob/master/README.md)
Outstanding features:
  - container-routing-integrity
  - native-garden-runc
  - loggregator-forwarder-agent
  - dns-service-discovery
  - routing-api

Features no longer able to be supported:
  - cflinuxfs2
  - local-ha-db
  - autoscaler & autoscaler-postgres

Also updated the new hook partially.
Flushed out the hooks better, but new isn't fully resolved yet

Got the exodus data set for autoscaler.

Still needs some love on the external databases
Also, added funtionality for the missing addons, extracted
enable-service-discovery to an overlay because of a conflict with
override-app-domains, and updated spec files.

Fixes genesis-community#130
Both the enable-service-discovery and override-app-domains change the
app_domains parameter, and in incompaptible ways.  This change makes
them work together in a way that spruce can merge any combination of
feature usage.
* Bump CA lifespan to 10y
The `bare` feature is intended to do nothing more that absolutely
required for Genesis to deploy upstream cf-deployment.  To preserve this
expectation, the best practice of 10-year CA expiry was moved to its own
overlay and included if `bare` feature is not specified.
- bbsdb uses diegodb_* params (backwards compatibility
- default usernames for all databases that match the database name (if a
  universal `params.external_db_username` not provided)
- fix *_port bosh-variables (was pointing to the corresponding host
  param instead of the port param)
- fixed defaults for loadbalancer and blobstore prompts
- updated to use `genesis_config_block`
- added missing api_domain params and exodus data
dennisjbell and others added 12 commits June 15, 2020 22:29
`info` hook script was hardcoding the system domain due to a
misunderstanding how the lookup of exodus values works.
No longer have to have the `move_secrets_to_credhub` function as it has
been made generally available via the bash helpers script
- Fixed error in template
- removed debugging 'not' filter
- Check will see if the previous version is too old, and should check if
  the secrets are in the vault (TODO)
- Blueprint will add the manifest fragments for migrating
- Pre-deploy will move the secrets to credhub (and whatever else it
  needs to do)
If you specified outdated methods of turning on service discovery, the
blueprint script would tell you to use `enable-service-discover` while
making the change internally for the current run, but the correct
version was not actually ever whitelisted, so if you did correct it, it
would just fail.
@7hunderbird
Copy link
Author

To help #141.

@7hunderbird
Copy link
Author

OMG nevermind git! 👎

@7hunderbird 7hunderbird deleted the cfdb-prompt-141 branch July 22, 2020 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants