<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/doc/examples/cloud-config.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-02T21:21:00+00:00</updated>
<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>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>ssh exit with non-zero status on disabled user (#472)</title>
<updated>2020-07-15T18:21:02+00:00</updated>
<author>
<name>Eduardo Otubo</name>
<email>otubo@redhat.com</email>
</author>
<published>2020-07-15T18:21:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e161059a18173e2b61c54dba9eab774401fb5f1f'/>
<id>urn:sha1:e161059a18173e2b61c54dba9eab774401fb5f1f</id>
<content type='text'>
It is confusing for scripts, where a disabled user has been specified,
that ssh exits with a zero status by default without indication anything
failed.

I think exitting with a non-zero status would make more clear in scripts
and automated setups where things failed, thus making noticing the issue
and debugging easier.

Signed-off-by: Eduardo Otubo &lt;otubo@redhat.com&gt;
Signed-off-by: Aleksandar Kostadinov &lt;akostadi@redhat.com&gt;

LP: #1170059</content>
</entry>
<entry>
<title>Add schema to apt configure config (#357)</title>
<updated>2020-05-13T20:45:01+00:00</updated>
<author>
<name>lucasmoura</name>
<email>lucas.moura@canonical.com</email>
</author>
<published>2020-05-13T20:45:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=2e32c40a607250bc9e713c0daf360dc6617f4420'/>
<id>urn:sha1:2e32c40a607250bc9e713c0daf360dc6617f4420</id>
<content type='text'>
Create a schema object for the `apt_configure` module and
validate this schema in the `handle`  function of the module.

There are some considerations regarding this PR:

* The `primary` and `security` keys have the exact same properties. I
  tried to eliminate this redundancy by moving their properties to a
  common place and then just referencing it for both security and
  primary. Similar to what is documented here:
    https://json-schema.org/understanding-json-schema/structuring.html
  under the `Reuse` paragraph.  However, this approach does not work,
  because the `#` pointer goes to the beginning of the file, which is
  a python module instead of a json file, not allowing the pointer to
  find the correct definition. What I did was to create a separate dict
  for the mirror config and reuse it for primary and security, but
  maybe there are better approaches to do that.
* There was no documentation for the config `debconf_selections`. I
  tried to infer what it supposed to do by looking at the code and the
  `debconf-set-selections`  manpage, but my description may not be
  accurate or complete.
* Add a _parse_description function to schema.py to render multi-line
  preformatted content instead of squashing all whitespace

LP: #1858884</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>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>docs: note in rtd about avoiding /tmp when writing files</title>
<updated>2018-07-09T20:13:47+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-07-09T20:13:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=2e62cb8a6406309cbeb5f8d2aa00fb30e72e1cfc'/>
<id>urn:sha1:2e62cb8a6406309cbeb5f8d2aa00fb30e72e1cfc</id>
<content type='text'>
LP: #1727876
</content>
</entry>
<entry>
<title>Add support for setting hashed passwords</title>
<updated>2017-03-24T20:45:24+00:00</updated>
<author>
<name>Tore S. Lonoy</name>
<email>tore.lonoy@gmail.com</email>
</author>
<published>2016-11-04T10:38:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=21632972df034c200578e1fbc121a07f20bb8774'/>
<id>urn:sha1:21632972df034c200578e1fbc121a07f20bb8774</id>
<content type='text'>
This change will add support for hashed passwords in cc_set_passwords.
It checks if a password is a hash with by checking that it matches
in fairly safe way, and also that the password does not have a ":" in it.

chpasswd needs to know if the password is hashed or not, so two lists
is created so chpasswd is feed with the correct one.

LP: #1570325
</content>
</entry>
<entry>
<title>Fix minor docs typo: perserve &gt; preserve</title>
<updated>2017-01-13T01:00:55+00:00</updated>
<author>
<name>Jeremy Bicha</name>
<email>jbicha@ubuntu.com</email>
</author>
<published>2017-01-13T01:00:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e2274393b882c723ab93189c57e7e68a46e4e10f'/>
<id>urn:sha1:e2274393b882c723ab93189c57e7e68a46e4e10f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: change 'nobootwait' to 'nofail' in docs</title>
<updated>2016-12-19T19:23:27+00:00</updated>
<author>
<name>Anhad Jai Singh</name>
<email>ajaisingh@tower-research.com</email>
</author>
<published>2016-12-09T14:10:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=39fb5a0240597112af8162c6c3365288450a7a77'/>
<id>urn:sha1:39fb5a0240597112af8162c6c3365288450a7a77</id>
<content type='text'>
'nobootwait' is an upstart specific extension to the mount syntax that is
not supported by other mount systems.  As Ubuntu 16.04 moved from upstart
to systemd, support for 'nobootwait' was lost.

All examples using 'nobootwait' are updated to use the standard 'nofail',
which gives the expected behaviour of not failing to boot in case a volume
is missing. There are subtle differences in semantics between
'nobootwait' and 'nofail', but it is the best substitute that gives
behaviour similar to the upstart specific option.
</content>
</entry>
</feed>
