text stringlengths 7 369 |
|---|
[1689.06 --> 1690.32] It came with a two-year warranty, |
[1690.32 --> 1692.14] and there's apparently something called |
[1692.14 --> 1693.78] the Magnuson Moss Act, |
[1693.84 --> 1694.54] I think that's what it is. |
[1694.98 --> 1696.96] If they try and play funny buggers with it, |
[1697.04 --> 1698.54] I can quote them and say that, |
[1698.70 --> 1699.44] and apparently then |
[1699.44 --> 1700.28] they'll just capitulate |
[1700.28 --> 1701.48] and send me their replacement |
[1701.48 --> 1703.60] reconditioned drive |
[1703.60 --> 1704.58] because they can't prove |
[1704.58 --> 1706.00] that my shucking it broke it |
[1706.00 --> 1706.56] or something. |
[1707.44 --> 1708.86] Let's talk a little Ansible, |
[1709.04 --> 1710.60] one of our favorite topics here, |
[1710.72 --> 1712.40] and I think maybe one we should |
[1712.40 --> 1714.66] probably share a little more on the show |
[1714.66 --> 1716.16] as Brent begins his journey |
[1716.16 --> 1717.48] down the Ansible lane. |
[1717.48 --> 1718.60] But in the meantime, |
[1719.04 --> 1720.54] before we go down Ansible lane, |
[1720.62 --> 1721.84] maybe we should stop off |
[1721.84 --> 1723.48] on Bitwarden Drive. |
[1723.72 --> 1724.28] What do you got here? |
[1724.62 --> 1726.14] What about if I put some peanut butter |
[1726.14 --> 1726.90] with the chocolate? |
[1727.32 --> 1728.96] Yeah, that sounds perfect for me. |
[1729.06 --> 1730.08] And bring Ansible together |
[1730.08 --> 1731.08] with Bitwarden. |
[1731.28 --> 1731.76] How about that? |
[1731.82 --> 1732.12] Right. |
[1732.50 --> 1734.00] That sounds good, actually. |
[1734.52 --> 1736.24] There was a chat happening on Discord, |
[1736.40 --> 1737.40] I think it was this morning, |
[1738.08 --> 1740.22] where Orange, Jake, |
[1740.40 --> 1742.02] who was on the show a little while ago, |
[1742.08 --> 1742.96] was talking about |
[1742.96 --> 1745.10] how he uses Ansible Vault |
[1745.10 --> 1746.66] crossed with Bitwarden. |
[1746.66 --> 1748.34] There is a reference |
[1748.34 --> 1749.50] to one of my favorite |
[1749.50 --> 1751.04] bash.org moments |
[1751.04 --> 1753.18] where his demo password |
[1753.18 --> 1753.94] is hunter2. |
[1754.14 --> 1754.94] Those that know, |
[1755.08 --> 1756.62] know about that one. |
[1757.88 --> 1758.46] But essentially, |
[1758.72 --> 1759.86] what this allows me to do |
[1759.86 --> 1762.34] is use Bitwarden |
[1762.34 --> 1763.92] as my credential store |
[1763.92 --> 1765.32] for my Ansible Vault |
[1765.32 --> 1766.42] encryption password. |
[1766.92 --> 1768.10] So all of my secrets |
[1768.10 --> 1769.50] remain encrypted |
[1769.50 --> 1770.56] using Ansible Vault |
[1770.56 --> 1772.56] with 256-bit blah, blah, blah |
[1772.56 --> 1774.24] as a file that I store |
[1774.24 --> 1775.62] version controlled in Git. |
[1775.62 --> 1776.96] And what I'm doing now |
[1776.96 --> 1777.72] is rather than having |
[1777.72 --> 1778.88] a clear text file |
[1778.88 --> 1779.72] sitting on disk |
[1779.72 --> 1780.90] to decrypt that file, |
[1781.10 --> 1782.22] I am now using |
[1782.22 --> 1783.60] the Bitwarden CLI |
[1783.60 --> 1784.76] to connect |
[1784.76 --> 1786.92] the Vault password |
[1786.92 --> 1788.60] that I've now put in Bitwarden |
[1788.60 --> 1790.10] to unlock |
[1790.10 --> 1790.80] that |
[1790.80 --> 1792.64] encrypted file |
[1792.64 --> 1793.08] in Ansible. |
[1793.30 --> 1794.04] This feels like |
[1794.04 --> 1795.04] it could be pretty powerful. |
[1795.50 --> 1796.48] I think I'm understanding. |
[1796.82 --> 1796.84] But |
[1796.84 --> 1798.20] so essentially, |
[1798.32 --> 1798.98] as Ansible |
[1798.98 --> 1799.88] is setting up a machine, |
[1799.88 --> 1801.14] if it needs to deploy software |
[1801.14 --> 1802.14] that needs some sort of |
[1802.14 --> 1803.00] secret password |
[1803.00 --> 1804.18] or key, |
[1804.82 --> 1806.08] instead of having to put |
[1806.08 --> 1806.56] that somewhere |
[1806.56 --> 1807.74] in the Ansible config |
[1807.74 --> 1808.36] or whatever, |
[1809.10 --> 1810.08] there's now an option |
[1810.08 --> 1810.78] to have, |
[1811.12 --> 1812.30] as Ansible is deploying, |
[1812.80 --> 1814.38] use the Bitwarden CLI |
[1814.38 --> 1815.82] to look that password up |
[1815.82 --> 1817.12] and sort of insert |
[1817.12 --> 1817.64] that password |
[1817.64 --> 1818.70] as it's being deployed. |
[1819.06 --> 1819.50] Is that right? |
[1820.00 --> 1820.74] You could do that |
[1820.74 --> 1821.92] using the Lookup plugin, |
[1822.02 --> 1822.44] I think. |
[1822.66 --> 1823.96] But the way that we're doing it |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.