vyos-cloud-init.git/doc/examples, branch crux

config: disable ssh access to a configured user account

2018-09-08T01:48:38+00:00

Cloud config can now disable ssh access to non-root users. When defining the 'users' list in cloud-configuration a boolean 'ssh_redirect_user: true' can be provided to disable ssh logins for that user. Any ssh 'public-keys' defined in cloud meta-data will be added and disabled in .ssh/authorized_keys. Any attempts to ssh as this user using acceptable ssh keys will be presented with a message like the following: Please login as the user "ubuntu" rather than the user "youruser".

docs: note in rtd about avoiding /tmp when writing files

2018-07-09T20:13:47+00:00

LP: #1727876

Explicitly prevent `sudo` access for user module

2018-06-19T22:04:17+00:00

To deny a user elevated access, you can omit the `sudo` key from the `users` dictionary. This works fine however it's implicitly defined based on defaults of `cloud-init`. If the project moves to have `sudo` access allowed for all by default (quite unlikely but still possible) this will catch a few people out. This introduces the ability to define an explicit `sudo: False` in the `users` dictionary and it will prevent `sudo` access. The behaviour is identical to omitting the key. LP: #1771468

DataSourceSmartOS: change default fs on ephemeral disk from ext3 to ext4.

2018-04-18T17:14:31+00:00

ext3 is not able to support file system sizes that are needed in Joyent's cloud. For the default block size of 4k, the maximum filesystem size for ext3 is 2^32 * 4096 = 16 TiB. This changes the default file system type from ext3 to ext4. LP: #1763511

correct documentation to match correct attribute name usage.

2018-04-03T18:19:54+00:00

LP: #1420018

doc: fix chef install from apt packages example in RTD.

2018-02-26T22:17:46+00:00

Apt key was mistyped in the example. Should be apt: sources: source1: instead of apt: source1: source:

schema: Log debug instead of warning when jsonschema is not available.

2017-10-18T20:10:06+00:00

When operating in expected path, cloud-init should avoid logging with warning. That causes 'WARNING' messages in /var/log/cloud-init.log. By default, warnings also go to the console. Since jsonschema is a optional dependency, and not present on xenial and zesty, cloud-init should not warn there. Also here: * Add a test to integration tests to assert that there are no warnings in /var/log/cloud-init.log. * Update one integration test that did show warning and the related documentation and examples. LP: #1724354

chef: Add option to pin chef omnibus install version

2017-09-14T04:22:25+00:00

Most users of chef will want to pin the version that is installed. Typically new versions of chef have to be evaluated for breakage etc. This change proposes a new optional `omnibus_version` field to the chef configuration. The changeset also adds documentation referencing the new field. LP: #1462693

doc: fix disk setup example table_type options

2017-07-17T13:40:23+00:00

This fixes the disk setup example doc which specifies that the only currently supported table_type option is 'mbr' by adding the 'gpt' option which got supported as of 0.7.7. LP: #1703789

Chef: Update omnibus url to chef.io, minor doc changes.

2017-06-08T19:40:46+00:00

- Updated to standard chef.io url - Removed the port 4000, due to that has been deprecated - Added Note about the run_list not being required Signed-off-by: JJ Asghar