Wrapped the salt-cloud feature tables in custom containers

Coupling the rST source to an HTML class is less than ideal but we need
to restrict the width here so...
This commit is contained in:
Seth House 2014-05-13 12:55:21 -06:00
parent d6b522a7f1
commit e8f55f9723

View File

@ -34,6 +34,8 @@ Standard Features
=================
These are features that are available for almost every provider.
.. container:: scrollable
+-----------------------+--------+----------+-------+---+------+------+------+---------+---------+---------+-------+---------+---------+
| |AWS |CloudStack|Digital|EC2|GoGrid|JoyEnt|Linode|OpenStack|Parallels|Rackspace|Saltify|Softlayer|Softlayer|
| |(Legacy)| |Ocean | | | | | | |(Legacy) | | |Hardware |
@ -64,6 +66,8 @@ instance name to be passed in. For example:
# salt-cloud -a attach_volume ami.example.com
.. container:: scrollable
+-----------------------+--------+----------+-------+---+------+------+------+---------+---------+---------+-------+---------+---------+
|Actions |AWS |CloudStack|Digital|EC2|GoGrid|JoyEnt|Linode|OpenStack|Parallels|Rackspace|Saltify|Softlayer|Softlayer|
| |(Legacy)| |Ocean | | | | | | |(Legacy) | | |Hardware |
@ -114,6 +118,8 @@ require the name of the provider to be passed in. For example:
# salt-cloud -f list_images my_digitalocean
.. container:: scrollable
+-----------------------+--------+----------+-------+---+------+------+------+---------+---------+---------+-------+---------+---------+
|Functions |AWS |CloudStack|Digital|EC2|GoGrid|JoyEnt|Linode|OpenStack|Parallels|Rackspace|Saltify|Softlayer|Softlayer|
| |(Legacy)| |Ocean | | | | | | |(Legacy) | | |Hardware |
@ -186,4 +192,3 @@ require the name of the provider to be passed in. For example:
+-----------------------+--------+----------+-------+---+------+------+------+---------+---------+---------+-------+---------+---------+
|show_volume | | | |Yes| | | | | | | | | |
+-----------------------+--------+----------+-------+---+------+------+------+---------+---------+---------+-------+---------+---------+