![plain text workflow plain text workflow](https://www.alfredapp.com/blog/tips-and-tricks/manipulating-selected-text-in-macos-with-alfred-workflows/selection-pasted-plain-text.png)
I've tried converting it with the command above (works with other apis) and it fails. I've tried just sending the parameter value, and it fails. For instance if I get the parameter and then convert it with "ConvertTo-SecureString –string $StoredPW –AsPlainText -Force", then I can use the stored parameter for some APIs.īut now I'm working with an api that seems it really wants the clear text password.
#PLAIN TEXT WORKFLOW PASSWORD#
I see that for some services, I can connect using a password stored this way, I guess if the API accepts a securestring it works. The workflow definition stores the parameter value in encrypted form using an encryption key provided by the Active Roles service Per documentation the SecureString syntax used for storing workflow parameters: I want to save the password in the workflow as syntax type SecureString, so that the password's hidden in the workflow properties. I'm writing a powershell script that connects via api to a vendor tool.
#PLAIN TEXT WORKFLOW SOFTWARE#
The Docs as Code concepts are widely practiced in the software industry,Īnd are gaining adoption in the writing community. Marcia Riefer Johnston and Dave May from Amazon Web Services (AWS) told the story of their team’s move to docs as code: what worked, what didn’t, what’s next.Swapnil Ogale provided his take on transitioning from traditional tech writing tools to a docs as code approach.Diana Lakatos showed various fully remote processes platformOS developed to help community members contribute content and code to their developer portal, including why they follow the docs as code approach, how they developed an editorial workflow that can work for all contributors, and how they implemented it through GitHub.Jen Lambourne shared the UK Government Digital Service’s experience adopting a docs as code approach.Predrag Mandic talked about how the “documentation is code” principle saves money and time, empowers documentarians, simplifies processes around testing documentation and brings happiness to a diverse customer base.Jodie Putrino from F5 gave a practical account of her experience developing docs like code.Rachel Whitten from Pantheon give a talk on their implementation of these approaches.Margaret Eker and Jennifer Roundeau from Rackspace & Capital One, it was a great overview of Docs as Code.We had a panel with folks from Rackspace, Microsoft, Balsamiq, and Twitter, all talking about how they are adopting these practices.Riona MacNamara talked about how adopting Docs as Code has completely transformed how Google does documentation.Write the Docs has had a number of talks that touch on this topic over the years. In addition, there is an open source tool-chain which shows how the docs-as-code approach can be implemented Modern Technical Writing - Andrew Etter.
![plain text workflow plain text workflow](https://formtrek.files.wordpress.com/2018/05/formtrek44.jpg)
There are a couple books we recommend that you check out:
![plain text workflow plain text workflow](https://1.bp.blogspot.com/-Dd_90FsXG9s/WRNoLdIK4uI/AAAAAAAADXE/PhDhbh7T6-Ahptz5ByHOKcS7ZozC92LuQCLcB/s1600/pic05_WorkflowEmailResult.jpg)
There is a lot more to building a proper Docs as Code workflow. You can block merging of new features if they don’t include documentation, which incentivizes developers to write about features while they are fresh.Developers will often write a first draft of documentation.Writers integrate better with development teams.Generally a Docs as Code approach gives you the following benefits: It enables a culture where writers and developers both feel ownership of documentation,Īnd work together to make it as good as possible. This means following the same workflows as development teams,Īnd being integrated in the product team. Plain Text Markup (Markdown, reStructuredText, Asciidoc).Eric Holscher & the Write the Docs communityĭocumentation as Code ( Docs as Code) refers to a philosophy that you should be writing documentation with the same tools as code: