<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/doc/examples, branch 20.4</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.4</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.4'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2020-10-30T20:12:38+00:00</updated>
<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/marekm72/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 cloud config on chef example (#551)</title>
<updated>2020-08-26T15:22:46+00:00</updated>
<author>
<name>lucasmoura</name>
<email>lucas.moura@canonical.com</email>
</author>
<published>2020-08-26T15:22:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=947a316a784580da0e91685b44635067e82e0038'/>
<id>urn:sha1:947a316a784580da0e91685b44635067e82e0038</id>
<content type='text'>
</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/marekm72/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>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/marekm72/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>Enable chef_license support for chef infra client (#389)</title>
<updated>2020-05-27T22:49:38+00:00</updated>
<author>
<name>Bipin Bachhao</name>
<email>bipinbachhao@gmail.com</email>
</author>
<published>2020-05-27T22:49:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=0919bd46bbd1b12158c369569ec1298bb000dd8a'/>
<id>urn:sha1:0919bd46bbd1b12158c369569ec1298bb000dd8a</id>
<content type='text'>
Co-authored-by: Daniel Watkins &lt;oddbloke@ubuntu.com&gt;</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/marekm72/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>Add test to ensure docs examples are valid cloud-init configs (#355)</title>
<updated>2020-05-08T21:38:51+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-05-08T21:38:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=34b868020254106af8c79ffb85e04e294b19e44f'/>
<id>urn:sha1:34b868020254106af8c79ffb85e04e294b19e44f</id>
<content type='text'>
Also update all examples to include the cloud-config header if they don't have it

LP: #1876414</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/marekm72/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>util: read_cc_from_cmdline handle urlencoded yaml content (#275)</title>
<updated>2020-03-25T14:01:11+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2020-03-25T14:01:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=3f6746c6113ec9f691ff7e4f5ed3764d4261373b'/>
<id>urn:sha1:3f6746c6113ec9f691ff7e4f5ed3764d4261373b</id>
<content type='text'>
Add support for additional escaping of formatting characters
in the YAML content between the 'cc:' and 'end_cc' tokens.  On
s390x legacy terminals the use of square brackets [] are not
available limiting the ability to indicate lists of values in
yaml content. Using #5B and #5D, [ and ] respectively enables
s390x users to pass list yaml content into cloud-init via
command line interface.</content>
</entry>
<entry>
<title>docs: mount_default_files is a list of 6 items, not 7 (#212)</title>
<updated>2020-02-14T02:48:34+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2020-02-14T02:48:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=c90932f5cb68e789636c5e6b0b74fceb1d38c6a4'/>
<id>urn:sha1:c90932f5cb68e789636c5e6b0b74fceb1d38c6a4</id>
<content type='text'>
</content>
</entry>
</feed>
