<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/doc/examples/cloud-config-user-groups.txt, branch rolling</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2022-02-10T21:44:37+00:00</updated>
<entry>
<title>minor improvements to documentation (#1259)</title>
<updated>2022-02-10T21:44:37+00:00</updated>
<author>
<name>Mark Esler</name>
<email>eslerm@umn.edu</email>
</author>
<published>2022-02-10T21:44:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=cbe840ac7247c9bf79cf63100b7f85ef38758763'/>
<id>urn:sha1:cbe840ac7247c9bf79cf63100b7f85ef38758763</id>
<content type='text'>
* Primarily improved grammar for clarity.
* A few Sphinx/RST syntax fixes.
* Set text width to 79 characters per footer documentation
  where needed.
* Changed "yaml" to "YAML" when used in sentences.</content>
</entry>
<entry>
<title>spell check docs with spellintian (#1223)</title>
<updated>2022-02-02T21:21:00+00:00</updated>
<author>
<name>Brett Holman</name>
<email>bholman.devel@gmail.com</email>
</author>
<published>2022-02-02T21:21:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=7522845dfe8851b7b4f3e9924810b9ccf282bb6e'/>
<id>urn:sha1:7522845dfe8851b7b4f3e9924810b9ccf282bb6e</id>
<content type='text'>
Fix spelling errors

- Add Makefile target that checks for spelling errors
- Add Makefile target that fixes spelling errors
- Add spelling check to travis doc tests
- Fix various spelling errors in the docs </content>
</entry>
<entry>
<title>Remove invalid ssh_import_id from examples (#1031)</title>
<updated>2021-09-24T20:22:57+00:00</updated>
<author>
<name>James Falcon</name>
<email>therealfalcon@gmail.com</email>
</author>
<published>2021-09-24T20:22:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=8cebc449812b4bff4afaa0837b140030c419f98e'/>
<id>urn:sha1:8cebc449812b4bff4afaa0837b140030c419f98e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[examples] config-user-groups expire in the future (#902)</title>
<updated>2021-05-14T20:25:55+00:00</updated>
<author>
<name>Geert Stappers</name>
<email>stappers@stappers.it</email>
</author>
<published>2021-05-14T20:25:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=21a0b12052691d6634d0848dfa353c12939945e9'/>
<id>urn:sha1:21a0b12052691d6634d0848dfa353c12939945e9</id>
<content type='text'>
Changed year 2012 into 2032</content>
</entry>
<entry>
<title>Correct documentation and testcase data for some user-data YAML (#618)</title>
<updated>2020-10-30T20:12:38+00:00</updated>
<author>
<name>dermotbradley</name>
<email>dermot_bradley@yahoo.com</email>
</author>
<published>2020-10-30T20:12:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f8c84aeead77b7e508644d94889ee701f20e8d31'/>
<id>urn:sha1:f8c84aeead77b7e508644d94889ee701f20e8d31</id>
<content type='text'>
For cc_users_groups the user setting "expiredate" must be quoted in
order for the relevant flag and value to be then passed to the useradd
command. It its vaiue is not quoted then it is treated as Python type
datetime.date and in `cloudinit/distros/__init__.py` the below "is it a
string" condition fails and so no "--expiredate" parameter is passed to
useradd and therefore it has no effect:

```
if key in useradd_opts and val and isinstance(val, str):
    useradd_cmd.extend([useradd_opts[key], val])
```

For cc_users_groups, the user setting "inactive" does not actually
disable accounts, the useradd "--inactive" option actually defines the
number of days after password expiry that users can still login. So I
have changed the docs to show it taking a quoted value of days (which
works with the current code) rather than a boolean value.  The quotes
are necessary, like expiredate above, so that the value is also passed
to the useradd command.

For cc_power_state_change.py the "delay" setting value needs to have
quotes around it as otherwise its leading plus sign will be stripped
off.</content>
</entry>
<entry>
<title>Fix 'Users and Groups' configuration documentation (#530)</title>
<updated>2020-08-13T17:32:09+00:00</updated>
<author>
<name>sshedi</name>
<email>53473811+sshedi@users.noreply.github.com</email>
</author>
<published>2020-08-13T17:32:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4fb7eab7989b8eb80b4451ea325311c5dc97e3bc'/>
<id>urn:sha1:4fb7eab7989b8eb80b4451ea325311c5dc97e3bc</id>
<content type='text'>
Few of the 'User and Groups' configurations in cloud-config have no effect on
already existing users. This was not documented earlier.

This change set adds that information to documentation.

Signed-off-by: Shreenidhi Shedi &lt;sshedi@vmware.com&gt;</content>
</entry>
<entry>
<title>YAML align indent sizes for docs readability  (#323)</title>
<updated>2020-04-22T18:38:15+00:00</updated>
<author>
<name>Tak Nishigori</name>
<email>nishigori.tak@gmail.com</email>
</author>
<published>2020-04-22T18:38:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1b049e6e51a9ac1ca02bf33629ede5c47c5b1941'/>
<id>urn:sha1:1b049e6e51a9ac1ca02bf33629ede5c47c5b1941</id>
<content type='text'>
This proposal has been aligned in a human readable.

    There are no changes to this except for spac
    The indentation size is not specifically defined in the YAML RFC
        $ make yaml has passed on my-machine

I set the indentation size to the largest number of articles in the repository (dictionary: 2)

(And also include nishigori as a CLA signer.)</content>
</entry>
<entry>
<title>Add missing #cloud-config comment on first example in documentation.</title>
<updated>2019-08-20T15:01:45+00:00</updated>
<author>
<name>Florian Müller</name>
<email>florian.mueller@hetzner-cloud.de</email>
</author>
<published>2019-08-20T15:01:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3e998276e42f5e2a4fa3a09becc9f120363e22de'/>
<id>urn:sha1:3e998276e42f5e2a4fa3a09becc9f120363e22de</id>
<content type='text'>
Since this is the first code snippet some users might see,
they could end up in the same situation like me today
when they wonder why their yaml user config is not
working at all.
</content>
</entry>
<entry>
<title>config: disable ssh access to a configured user account</title>
<updated>2018-09-08T01:48:38+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-09-08T01:48:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=757247f9ff2df57e792e29d8656ac415364e914d'/>
<id>urn:sha1:757247f9ff2df57e792e29d8656ac415364e914d</id>
<content type='text'>
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".
</content>
</entry>
<entry>
<title>Explicitly prevent `sudo` access for user module</title>
<updated>2018-06-19T22:04:17+00:00</updated>
<author>
<name>Jacob Bednarz</name>
<email>jacob.bednarz@gmail.com</email>
</author>
<published>2018-06-19T22:04:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4d69fb44a5607e16843537be26758893f2dd79be'/>
<id>urn:sha1:4d69fb44a5607e16843537be26758893f2dd79be</id>
<content type='text'>
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
</content>
</entry>
</feed>
