Basic Plan - basic update
jasonmimick opened this issue · comments
Ensure update-service works for the Basic Plan.
Document which properties of which resources are editable.
Validate customer needs around service update, e.g. scale cluster
See MVP doc.
Support for the following items have been requested.
- Review with Manulife to prioritize and rank.
- start/stop/pause cluster - try for 15th drop (ensure backups by default - 15th drop)
- scale cluster - supported.
- enable/disable backup - ensure that some kind of backup is enabled by default; then more advance configuration/update for the backup schedule.
Known supported updates:
- Scale cluster size, e.g M20 -> M30
Should follow spec for json patch data here for testing various update scenarios: https://docs.atlas.mongodb.com/reference/api/clusters-modify-one/
eg
cf update-service chewy-123 -c '{ "paused":"true" }'
or is it?
cf update-service chewy-123 -c '{"cluster": { "paused":"true" } }'
@vasilevp please check this - last feature we need for release
Update is working, here is an example to pause a cluster.
cf update-service wed-demo-1 -c '{ "paused":true }'
Updating service instance wed-demo-1 as admin...
OK
➜ atlas-osb-MASTER-DEMO git:(master) ✗ mongocli atlas clusters list --projectId 5f0f0e0859cd8a08718294bf | jq '.[] | { "n" : .name, "s" : .paused}'
{
"n": "wed-demo-1",
"s": true
}